SDD Observatory
Stars
2.8K
Contributors
60
Open issues
49
Age
2.7 years
Last push
yesterday
Latest release
v2.28.0 Jul 27, 2026
Week of Aug 31, 2025: 0 commits Week of Sep 7, 2025: 0 commits Week of Sep 14, 2025: 8 commits Week of Sep 21, 2025: 1 commit 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: 1 commit Week of Oct 26, 2025: 0 commits Week of Nov 2, 2025: 3 commits Week of Nov 9, 2025: 0 commits Week of Nov 16, 2025: 2 commits Week of Nov 23, 2025: 1 commit Week of Nov 30, 2025: 0 commits Week of Dec 7, 2025: 1 commit Week of Dec 14, 2025: 1 commit Week of Dec 21, 2025: 0 commits Week of Dec 28, 2025: 0 commits Week of Jan 4, 2026: 1 commit Week of Jan 11, 2026: 1 commit Week of Jan 18, 2026: 0 commits Week of Jan 25, 2026: 1 commit Week of Feb 1, 2026: 9 commits Week of Feb 8, 2026: 0 commits Week of Feb 15, 2026: 8 commits Week of Feb 22, 2026: 1 commit Week of Mar 1, 2026: 1 commit Week of Mar 8, 2026: 0 commits Week of Mar 15, 2026: 0 commits Week of Mar 22, 2026: 1 commit Week of Mar 29, 2026: 14 commits Week of Apr 5, 2026: 0 commits Week of Apr 12, 2026: 0 commits Week of Apr 19, 2026: 9 commits Week of Apr 26, 2026: 1 commit Week of May 3, 2026: 1 commit Week of May 10, 2026: 1 commit Week of May 17, 2026: 0 commits Week of May 24, 2026: 1 commit Week of May 31, 2026: 0 commits Week of Jun 7, 2026: 0 commits Week of Jun 14, 2026: 0 commits Week of Jun 21, 2026: 0 commits Week of Jun 28, 2026: 0 commits Week of Jul 5, 2026: 3 commits Week of Jul 12, 2026: 6 commits Week of Jul 19, 2026: 5 commits Week of Jul 26, 2026: 5 commits Week of Aug 2, 2026: 2 commits Week of Aug 9, 2026: 0 commits Week of Aug 16, 2026: 12 commits Week of Aug 23, 2026: 1 commit
Commits per week, last 12 months · 102 total
View weekly commit data
Week startingCommits
Aug 23, 20261
Aug 16, 202612
Aug 9, 20260
Aug 2, 20262
Jul 26, 20265
Jul 19, 20265
Jul 12, 20266
Jul 5, 20263
Jun 28, 20260
Jun 21, 20260
Jun 14, 20260
Jun 7, 20260
May 31, 20260
May 24, 20261
May 17, 20260
May 10, 20261
May 3, 20261
Apr 26, 20261
Apr 19, 20269
Apr 12, 20260
Apr 5, 20260
Mar 29, 202614
Mar 22, 20261
Mar 15, 20260
Mar 8, 20260
Mar 1, 20261
Feb 22, 20261
Feb 15, 20268
Feb 8, 20260
Feb 1, 20269
Jan 25, 20261
Jan 18, 20260
Jan 11, 20261
Jan 4, 20261
Dec 28, 20250
Dec 21, 20250
Dec 14, 20251
Dec 7, 20251
Nov 30, 20250
Nov 23, 20251
Nov 16, 20252
Nov 9, 20250
Nov 2, 20253
Oct 26, 20250
Oct 19, 20251
Oct 12, 20250
Oct 5, 20250
Sep 28, 20250
Sep 21, 20251
Sep 14, 20258
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
Two subdirectories: plans/ holds three date-prefixed implementation plans (e.g. 2026-07-13-enrich-session-name.md, up to ~1,100 lines of checkbox task steps that invoke superpowers:subagent-driven-development) and specs/ holds the three matching design docs (e.g. 2026-07-13-enrich-session-name-design.md).

Assessment drift: low

Spec-to-code drift

Low, with an unusual shape: the entire docs/superpowers/ tree landed in one squashed PR (2026-07-14) together with the code it describes, and the shipped sesh rename --enrich feature closely matches its 2026-07-13 design (seshcli/rename.go, a new github package, and namer/sanitize.go all appear as planned). But two of the three plan/spec pairs — the 2026-06-27 sesh status command and status-cache designs — describe status-bar and cache machinery the final design explicitly replaced, and the shipped design’s own header still reads Status: proposed. The retained superseded plans read as design history rather than live spec.

Defects and rework

The spec corpus itself documents one full rework cycle: roughly 2,200 lines of June planning for a tmux status-bar feature (with a status cache and background refresher) were scrapped in favor of the far simpler session-name enrichment in the 2026-07-13 design, whose motivation notes the replacement “collapses the feature to a single command”. Defect trends since the merge are not yet assessed — the feature is days old.

Maintenance outcomes

Too early to judge — the framework artifacts were five days old at first review. The project itself is actively maintained (a fix merged three days after the spec commit, and regular tagged releases, most recently v2.27.0), so future reviews can watch whether subsequent features route through docs/superpowers/ or the directory stays a one-PR artifact.

Timeline

  1. Superpowers artifacts land on `main`

    All six plan/spec files merged in a single squashed PR — "Enrich tmux session names with GitHub issue titles (#408)" — alongside the implementation they describe.

  2. Design work begins

    Earliest date carried by the plan/spec files — the `sesh status` and status-cache pairs are both dated 2026-06-27 in their filenames.

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