SDD Observatory
Stars
4.2K
Contributors
17
Open issues
126
Age
7 months
Last push
today
Latest release
v0.27.0 Aug 24, 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: 3 commits Week of Feb 8, 2026: 19 commits Week of Feb 15, 2026: 0 commits Week of Feb 22, 2026: 24 commits Week of Mar 1, 2026: 31 commits Week of Mar 8, 2026: 32 commits Week of Mar 15, 2026: 36 commits Week of Mar 22, 2026: 38 commits Week of Mar 29, 2026: 26 commits Week of Apr 5, 2026: 32 commits Week of Apr 12, 2026: 37 commits Week of Apr 19, 2026: 39 commits Week of Apr 26, 2026: 30 commits Week of May 3, 2026: 21 commits Week of May 10, 2026: 44 commits Week of May 17, 2026: 60 commits Week of May 24, 2026: 39 commits Week of May 31, 2026: 15 commits Week of Jun 7, 2026: 50 commits Week of Jun 14, 2026: 40 commits Week of Jun 21, 2026: 33 commits Week of Jun 28, 2026: 49 commits Week of Jul 5, 2026: 29 commits Week of Jul 12, 2026: 76 commits Week of Jul 19, 2026: 29 commits Week of Jul 26, 2026: 91 commits Week of Aug 2, 2026: 95 commits Week of Aug 9, 2026: 88 commits Week of Aug 16, 2026: 57 commits Week of Aug 23, 2026: 73 commits
Commits per week, last 12 months · 1.2K total
View weekly commit data
Week startingCommits
Aug 23, 202673
Aug 16, 202657
Aug 9, 202688
Aug 2, 202695
Jul 26, 202691
Jul 19, 202629
Jul 12, 202676
Jul 5, 202629
Jun 28, 202649
Jun 21, 202633
Jun 14, 202640
Jun 7, 202650
May 31, 202615
May 24, 202639
May 17, 202660
May 10, 202644
May 3, 202621
Apr 26, 202630
Apr 19, 202639
Apr 12, 202637
Apr 5, 202632
Mar 29, 202626
Mar 22, 202638
Mar 15, 202636
Mar 8, 202632
Mar 1, 202631
Feb 22, 202624
Feb 15, 20260
Feb 8, 202619
Feb 1, 20263
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
docs/superpowers/
Formats
Markdown
Notes
143 Markdown files in three subdirectories: plans/ holds 72 dated implementation plans (checkbox task lists that invoke superpowers:executing-plans), specs/ holds 70 matching design docs suffixed -design.md, and release-notes/ holds one entry. Files pair up under a YYYY-MM-DD-<topic> convention, e.g. 2026-05-18-log-persistence.md and 2026-05-18-log-persistence-design.md.

Assessment drift: moderate

Spec-to-code drift

Moderate. The spec tree has been frozen since 2026-05-23 while the project ships at high tempo — four releases (v0.19.1 through v0.22.0) landed in the eight weeks since, none adding plans or specs here. The staleness looks like deliberate process migration rather than neglect: a May 2026 curation pass verified the docs and deleted ten stale ones, and AGENTS.md now routes new design work through docs/adr/ (active through 2026-07-17) and spec-labelled GitHub issues, leaving docs/superpowers/ as an archive of completed work that newer code no longer updates.

Defects and rework

Rework was routed back through the same spec workflow rather than patched ad hoc: bug fixes got their own plan/design pairs (e.g. 2026-03-23-session-memory-leak-fix, 2026-04-02-grok-issues-fix), and plans embed test-first checkboxes (“write failing test” steps) per task. Whether spec-driven changes regressed less than untracked ones is not yet assessed.

Maintenance outcomes

A striking velocity case: from template initialization (2026-02-06) to a released multi-provider product (v0.22.0 by 2026-07-15) in about five months, with roughly 70 design docs covering the buildout across 11 contributors. The specs stayed load-bearing after implementation — the living AGENTS.md architecture guide cites individual design docs (e.g. 2026-04-13-session-actor-design.md) as the reference for subsystems. The open question is the migration away from the tracked directory: whether ADRs plus issue-tracked specs preserve the same spec-to-code traceability.

Timeline

  1. Latest spec activity

    Commit #620 ("fix(logging): move log directory out of the projects root + harden migration and agent sandbox", translated) touched the log-persistence plan and spec; the tree has been static since.

  2. Spec tree consolidated and curated

    Commit #595 ("docs: verify and clean up outdated design documents", translated) renamed 36 legacy `docs/plans/` files into `docs/superpowers/` and deleted 10 stale docs.

  3. `docs/superpowers/` directory created

    First files on the tracked path — an Alembic best-practices plan and design doc — landed in commit #115.

  4. Superpowers workflow present from the first commit

    The initial commit (`chore: initialize project from template`) already carried dated plans and design docs under the earlier `docs/plans/` path, the oldest dated 2026-01-21 — spec-first from day one.

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