SDD Observatory
Stars
4.1K
Contributors
18
Open issues
283
Age
7 months
Last push
today
Latest release
v0.9.3 Aug 26, 2026
Week of Aug 31, 2025: 0 commits Week of Sep 7, 2025: 0 commits Week of Sep 14, 2025: 0 commits Week of Sep 21, 2025: 0 commits Week of Sep 28, 2025: 0 commits Week of Oct 5, 2025: 0 commits Week of Oct 12, 2025: 0 commits Week of Oct 19, 2025: 0 commits Week of Oct 26, 2025: 0 commits Week of Nov 2, 2025: 0 commits Week of Nov 9, 2025: 0 commits Week of Nov 16, 2025: 0 commits Week of Nov 23, 2025: 0 commits Week of Nov 30, 2025: 0 commits Week of Dec 7, 2025: 0 commits Week of Dec 14, 2025: 0 commits Week of Dec 21, 2025: 0 commits Week of Dec 28, 2025: 0 commits Week of Jan 4, 2026: 0 commits Week of Jan 11, 2026: 0 commits Week of Jan 18, 2026: 0 commits Week of Jan 25, 2026: 0 commits Week of Feb 1, 2026: 42 commits Week of Feb 8, 2026: 55 commits Week of Feb 15, 2026: 35 commits Week of Feb 22, 2026: 39 commits Week of Mar 1, 2026: 63 commits Week of Mar 8, 2026: 46 commits Week of Mar 15, 2026: 83 commits Week of Mar 22, 2026: 85 commits Week of Mar 29, 2026: 59 commits Week of Apr 5, 2026: 56 commits Week of Apr 12, 2026: 113 commits Week of Apr 19, 2026: 335 commits Week of Apr 26, 2026: 248 commits Week of May 3, 2026: 254 commits Week of May 10, 2026: 195 commits Week of May 17, 2026: 175 commits Week of May 24, 2026: 184 commits Week of May 31, 2026: 193 commits Week of Jun 7, 2026: 227 commits Week of Jun 14, 2026: 149 commits Week of Jun 21, 2026: 185 commits Week of Jun 28, 2026: 79 commits Week of Jul 5, 2026: 108 commits Week of Jul 12, 2026: 190 commits Week of Jul 19, 2026: 301 commits Week of Jul 26, 2026: 409 commits Week of Aug 2, 2026: 269 commits Week of Aug 9, 2026: 157 commits Week of Aug 16, 2026: 183 commits Week of Aug 23, 2026: 121 commits
Commits per week, last 12 months · 4.6K total
View weekly commit data
Week startingCommits
Aug 23, 2026121
Aug 16, 2026183
Aug 9, 2026157
Aug 2, 2026269
Jul 26, 2026409
Jul 19, 2026301
Jul 12, 2026190
Jul 5, 2026108
Jun 28, 202679
Jun 21, 2026185
Jun 14, 2026149
Jun 7, 2026227
May 31, 2026193
May 24, 2026184
May 17, 2026175
May 10, 2026195
May 3, 2026254
Apr 26, 2026248
Apr 19, 2026335
Apr 12, 2026113
Apr 5, 202656
Mar 29, 202659
Mar 22, 202685
Mar 15, 202683
Mar 8, 202646
Mar 1, 202663
Feb 22, 202639
Feb 15, 202635
Feb 8, 202655
Feb 1, 202642
Jan 25, 20260
Jan 18, 20260
Jan 11, 20260
Jan 4, 20260
Dec 28, 20250
Dec 21, 20250
Dec 14, 20250
Dec 7, 20250
Nov 30, 20250
Nov 23, 20250
Nov 16, 20250
Nov 9, 20250
Nov 2, 20250
Oct 26, 20250
Oct 19, 20250
Oct 12, 20250
Oct 5, 20250
Sep 28, 20250
Sep 21, 20250
Sep 14, 20250
Sep 7, 20250
Aug 31, 20250

Metrics updated Aug 27, 2026 · collected automatically from the GitHub API

Spec structure

Location
openspec/
Formats
Markdown, YAML, JSON
Notes
Roughly 4,200 files. specs/ holds about 395 capability specs (e.g. agent-task-center, capability-aware-policy-router), and changes/ holds 26 active change folders plus an archive/ of about 598 completed ones — each with proposal.md, design.md, tasks.md and spec deltas, often a verification.md and .openspec.yaml. config.yaml pins OpenSpec CLI 1.3.x planning context and quality gates; docs/ holds about 25 dated audit, regression and manual-test-matrix reports. Commit messages and some capability specs mix Chinese prose; project.md and the spec structure are English.

Assessment drift: none

Spec-to-code drift

None observed. More than 500 commits have touched openspec/ in the three months since the workspace landed, and the newest spec-path commit is same-day with the newest code commit on main — feature and fix commits are interleaved within minutes with chore(task): archive … commits that close the matching change folder. config.yaml mandates that behavior changes start from a change under openspec/changes/<change-id>/ and gates archiving on openspec validate --all --strict --no-interactive plus synced main specs. The one internal staleness signal is documentation lag: the snapshot counts in config.yaml (208 capabilities, 224 archived changes) trail the actual tree (about 395 and 598).

Defects and rework

Bug fixes flow through the same spec pipeline as features: 161 of the roughly 598 archived change folders are fix-prefixed, and 71 changes carry a verification.md. The docs/ directory keeps dated regression and audit artifacts — for example lazy-state-extension-regression-2026-06-11.md and several manual test matrices — and the archive includes a recurring retro change (2026-07-15-retro-weekly-code-change-spec-coverage-2026-07-15) that audits how much of the week’s code change was covered by specs.

Maintenance outcomes

Ten contributors have shipped tagged releases through v0.7.4 at a fast tempo while completing roughly 600 spec changes between February and July 2026 — several per day on average. Quality gates codified in config.yaml (npm run typecheck, Vitest suites, cargo test) apply to every archived change. Adoption is only five months old, so long-run maintenance conclusions are premature, but this is currently the highest spec-throughput OpenSpec project in the observatory.

Timeline

  1. Latest spec activity

    Commit `9da8688`, "feat(git): 完善多仓库提交工作区" (refine the multi-repository commit workspace), landed the same day as the latest code commits on `main`.

  2. OpenSpec workspace landed in the repository

    Commit `c80bb56`, "chore(workflow): 引入 OpenSpec 与 Trellis 团队协作基线" (introduce the OpenSpec and Trellis team collaboration baseline), imported the existing workspace wholesale — 300 files and about 87,000 lines — as the team-shared source of truth for proposals, specs and changes.

  3. Earliest archived change

    The oldest completed change folder in the workspace, `2026-02-11-add-kanban-linked-issues-and-bulk-delete`, dates from eight days after the repository was created — the OpenSpec workflow predates its public import.

Metrics updated Aug 27, 2026 · Assessment last reviewed Jul 19, 2026 · Added Jul 19, 2026 · How we track