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
/opsx:explore — optional no-stakes thinking partner to shape the idea
/opsx:propose — create openspec/changes/<id>/ with proposal, spec deltas, design, and tasks
/opsx:apply — implement the task checklist
/opsx:sync — reconcile artifacts with reality
/opsx:archive — archive the change and update the living specs
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