OpenSpec
The OpenSpec CLI and toolkit itself, developed with its own change-folder workflow — "OpenSpec is built with OpenSpec".
Reviewed 2 months ago · Jul 18, 2026
- Stars
- 66.9K
- Contributors
- 103
- Open issues
- 209
- Age
- 1.1 years
- Last push
- 5 hours ago
- Latest release
- v1.11.0 Aug 26, 2026
View weekly commit data
| Week starting | Commits |
|---|---|
| Aug 30, 2026 | 1 |
| Aug 23, 2026 | 12 |
| Aug 16, 2026 | 19 |
| Aug 9, 2026 | 24 |
| Aug 2, 2026 | 28 |
| Jul 26, 2026 | 30 |
| Jul 19, 2026 | 44 |
| Jul 12, 2026 | 22 |
| Jul 5, 2026 | 17 |
| Jun 28, 2026 | 4 |
| Jun 21, 2026 | 6 |
| Jun 14, 2026 | 0 |
| Jun 7, 2026 | 0 |
| May 31, 2026 | 8 |
| May 24, 2026 | 4 |
| May 17, 2026 | 3 |
| May 10, 2026 | 1 |
| May 3, 2026 | 10 |
| Apr 26, 2026 | 9 |
| Apr 19, 2026 | 5 |
| Apr 12, 2026 | 13 |
| Apr 5, 2026 | 8 |
| Mar 29, 2026 | 1 |
| Mar 22, 2026 | 0 |
| Mar 15, 2026 | 0 |
| Mar 8, 2026 | 0 |
| Mar 1, 2026 | 0 |
| Feb 22, 2026 | 8 |
| Feb 15, 2026 | 8 |
| Feb 8, 2026 | 0 |
| Feb 1, 2026 | 4 |
| Jan 25, 2026 | 30 |
| Jan 18, 2026 | 39 |
| Jan 11, 2026 | 14 |
| Jan 4, 2026 | 30 |
| Dec 28, 2025 | 6 |
| Dec 21, 2025 | 17 |
| Dec 14, 2025 | 4 |
| Dec 7, 2025 | 2 |
| Nov 30, 2025 | 0 |
| Nov 23, 2025 | 2 |
| Nov 16, 2025 | 8 |
| Nov 9, 2025 | 6 |
| Nov 2, 2025 | 4 |
| Oct 26, 2025 | 3 |
| Oct 19, 2025 | 13 |
| Oct 12, 2025 | 19 |
| Oct 5, 2025 | 17 |
| Sep 28, 2025 | 18 |
| Sep 21, 2025 | 7 |
| Sep 14, 2025 | 35 |
| Sep 7, 2025 | 32 |
Metrics updated Sep 1, 2026 · collected automatically from the GitHub API
Spec structure
- Location
openspec/- Formats
- Markdown
- Notes
specs/holds 36 capability spec directories (e.g.cli-init,artifact-graph);changes/holds in-flight change folders plus an archive; alsoconfig.yaml,explorations/,initiatives/, andwork/.
Assessment drift: none
Spec-to-code drift
None observed. The openspec/ directory was last modified the same day as the repository’s latest push, with 36
living capability specs and over a dozen changes in flight. Specs demonstrably move with the code — this is the
reference case for what healthy SDD looks like in the wild.
Defects and rework
Not yet assessed. As the flagship dogfooding case, an interesting question for a future review is how often archived changes get reopened or superseded — the change archive makes that unusually observable.
Maintenance outcomes
The project migrated its own workflow from the legacy command set to OPSX using its change-folder process, and the migration artifacts are visible in-tree. Surviving a breaking rebuild of your own methodology while using that methodology is a meaningful early signal, though the project is still under a year old.
Timeline
-
v1.6.0 "OPSX Update, Tool Support" released
The rebuilt artifact-guided OPSX workflow became the default.
-
Repository created