SDD Observatory
Stars
61.4K
Contributors
73
Open issues
449
Age
11 months
Last push
14 hours ago
Latest release
v1.6.0 Jul 10, 2026
Week of Jul 19, 2025: 0 commits Week of Jul 26, 2025: 0 commits Week of Aug 2, 2025: 29 commits Week of Aug 9, 2025: 73 commits Week of Aug 16, 2025: 25 commits Week of Aug 23, 2025: 8 commits Week of Aug 30, 2025: 15 commits Week of Sep 6, 2025: 32 commits Week of Sep 13, 2025: 35 commits Week of Sep 20, 2025: 7 commits Week of Sep 27, 2025: 18 commits Week of Oct 4, 2025: 17 commits Week of Oct 11, 2025: 19 commits Week of Oct 18, 2025: 13 commits Week of Oct 25, 2025: 3 commits Week of Nov 1, 2025: 4 commits Week of Nov 8, 2025: 6 commits Week of Nov 15, 2025: 8 commits Week of Nov 22, 2025: 2 commits Week of Nov 29, 2025: 0 commits Week of Dec 6, 2025: 2 commits Week of Dec 13, 2025: 4 commits Week of Dec 20, 2025: 17 commits Week of Dec 27, 2025: 6 commits Week of Jan 3, 2026: 30 commits Week of Jan 10, 2026: 14 commits Week of Jan 17, 2026: 39 commits Week of Jan 24, 2026: 30 commits Week of Jan 31, 2026: 4 commits Week of Feb 7, 2026: 0 commits Week of Feb 14, 2026: 8 commits Week of Feb 21, 2026: 8 commits Week of Feb 28, 2026: 0 commits Week of Mar 7, 2026: 0 commits Week of Mar 14, 2026: 0 commits Week of Mar 21, 2026: 0 commits Week of Mar 28, 2026: 1 commit Week of Apr 4, 2026: 8 commits Week of Apr 11, 2026: 13 commits Week of Apr 18, 2026: 5 commits Week of Apr 25, 2026: 9 commits Week of May 2, 2026: 10 commits Week of May 9, 2026: 1 commit Week of May 16, 2026: 3 commits Week of May 23, 2026: 4 commits Week of May 30, 2026: 8 commits Week of Jun 6, 2026: 0 commits Week of Jun 13, 2026: 0 commits Week of Jun 20, 2026: 6 commits Week of Jun 27, 2026: 4 commits Week of Jul 4, 2026: 17 commits Week of Jul 11, 2026: 20 commits
Commits per week, last 12 months · 585 total

Metrics updated Jul 18, 2026 · collected automatically from the GitHub API

Core approach

Each unit of work is a change folder under openspec/changes/ containing a proposal, requirement deltas (ADDED/MODIFIED blocks with WHEN/THEN scenarios), a design doc, and a task list. On completion the change is archived and its deltas merge into living specs under openspec/specs/. The workflow was recently rebuilt around the artifact-guided "OPSX" commands.

Workflow

  1. /opsx:explore — optional no-stakes thinking partner to shape the idea
  2. /opsx:propose — create openspec/changes/<id>/ with proposal, spec deltas, design, and tasks
  3. /opsx:apply — implement the task checklist
  4. /opsx:sync — reconcile artifacts with reality
  5. /opsx:archive — archive the change and update the living specs
  6. Expanded profile adds /opsx:new, /opsx:continue, /opsx:ff, /opsx:verify, /opsx:bulk-archive, /opsx:onboard

Supported tools

Strengths

  • Heavily dogfooded — the repo itself carries 36 live capability specs and over a dozen in-flight changes
  • Explicitly brownfield-friendly; artifacts are plain Markdown with no special syntax
  • Very broad tool support — 34 documented integrations via skills and slash commands
  • Stores (beta) share planning repos across teams and repositories for cross-repo features

Limitations

  • Fast-moving: the workflow was just rebuilt (legacy to OPSX), so guidance churn is real
  • The Stores multi-repo feature is still in beta
  • Requires Node.js 20.19+ and a global npm install
  • The spec-delta format (ADDED/MODIFIED requirement blocks) has its own conventions to learn

Tracked projects using OpenSpec

Notes

OpenSpec’s change-folder model is the clearest instance of “diff-based” specs: instead of one big spec that slowly rots, every change carries its own requirement deltas that merge into living specs on archive. It is also the best-dogfooded framework we track — OpenSpec is built with OpenSpec, and its spec directory moves on the same days as its code. GitHub code search finds roughly 8,000 openspec/changes proposal files across public repos, the largest observable adopter base of the frameworks tracked here.

Added Jul 18, 2026 · Assessment last reviewed Jul 18, 2026 · How we track