SDD Observatory

Spec Kitty emerging

Spec Kit descendant that extends spec, plan, and task generation into a governed, repository-native execution loop with work packages, isolated worktrees, review state, acceptance, and merge decisions.

Reviewed 3 months ago · Aug 1, 2026

Website GitHub · Priivacy-ai/spec-kitty Compare with other frameworks →

Stars
1.7K
Contributors
127
Open issues
982
Age
1 years
Last push
today
Latest release
v3.2.7 Sep 9, 2026
Week of Oct 19, 2025: 3 commits Week of Oct 26, 2025: 70 commits Week of Nov 2, 2025: 44 commits Week of Nov 9, 2025: 203 commits Week of Nov 16, 2025: 99 commits Week of Nov 23, 2025: 4 commits Week of Nov 30, 2025: 0 commits Week of Dec 7, 2025: 10 commits Week of Dec 14, 2025: 160 commits Week of Dec 21, 2025: 0 commits Week of Dec 28, 2025: 17 commits Week of Jan 4, 2026: 21 commits Week of Jan 11, 2026: 633 commits Week of Jan 18, 2026: 796 commits Week of Jan 25, 2026: 340 commits Week of Feb 1, 2026: 290 commits Week of Feb 8, 2026: 514 commits Week of Feb 15, 2026: 430 commits Week of Feb 22, 2026: 305 commits Week of Mar 1, 2026: 11 commits Week of Mar 8, 2026: 152 commits Week of Mar 15, 2026: 44 commits Week of Mar 22, 2026: 11 commits Week of Mar 29, 2026: 93 commits Week of Apr 5, 2026: 230 commits Week of Apr 12, 2026: 132 commits Week of Apr 19, 2026: 275 commits Week of Apr 26, 2026: 246 commits Week of May 3, 2026: 128 commits Week of May 10, 2026: 42 commits Week of May 17, 2026: 196 commits Week of May 24, 2026: 169 commits Week of May 31, 2026: 1095 commits Week of Jun 7, 2026: 347 commits Week of Jun 14, 2026: 270 commits Week of Jun 21, 2026: 309 commits Week of Jun 28, 2026: 325 commits Week of Jul 5, 2026: 317 commits Week of Jul 12, 2026: 488 commits Week of Jul 19, 2026: 534 commits Week of Jul 26, 2026: 559 commits Week of Aug 2, 2026: 618 commits Week of Aug 9, 2026: 718 commits Week of Aug 16, 2026: 912 commits Week of Aug 23, 2026: 527 commits Week of Aug 30, 2026: 1011 commits Week of Sep 6, 2026: 900 commits Week of Sep 13, 2026: 605 commits Week of Sep 20, 2026: 937 commits Week of Sep 27, 2026: 1369 commits Week of Oct 4, 2026: 2143 commits Week of Oct 11, 2026: 572 commits
Commits per week, last 12 months · 20.2K total
View weekly commit data
Week startingCommits
Oct 11, 2026572
Oct 4, 20262.1K
Sep 27, 20261.4K
Sep 20, 2026937
Sep 13, 2026605
Sep 6, 2026900
Aug 30, 20261K
Aug 23, 2026527
Aug 16, 2026912
Aug 9, 2026718
Aug 2, 2026618
Jul 26, 2026559
Jul 19, 2026534
Jul 12, 2026488
Jul 5, 2026317
Jun 28, 2026325
Jun 21, 2026309
Jun 14, 2026270
Jun 7, 2026347
May 31, 20261.1K
May 24, 2026169
May 17, 2026196
May 10, 202642
May 3, 2026128
Apr 26, 2026246
Apr 19, 2026275
Apr 12, 2026132
Apr 5, 2026230
Mar 29, 202693
Mar 22, 202611
Mar 15, 202644
Mar 8, 2026152
Mar 1, 202611
Feb 22, 2026305
Feb 15, 2026430
Feb 8, 2026514
Feb 1, 2026290
Jan 25, 2026340
Jan 18, 2026796
Jan 11, 2026633
Jan 4, 202621
Dec 28, 202517
Dec 21, 20250
Dec 14, 2025160
Dec 7, 202510
Nov 30, 20250
Nov 23, 20254
Nov 16, 202599
Nov 9, 2025203
Nov 2, 202544
Oct 26, 202570
Oct 19, 20253

Metrics updated Oct 15, 2026 · collected automatically from the GitHub API

Core approach

Builds on GitHub Spec Kit's specification → plan → tasks lineage, then adds canonical mission state and a runtime for executing it. Mission artifacts live under kitty-specs/; tasks become work packages that advance through lifecycle lanes in isolated .worktrees/. A next → review → accept → merge loop keeps implementation, acceptance criteria, review evidence, and merge decisions in Git, with a local dashboard and retrospective closing the loop.

Workflow

  1. spec-kitty init — install the selected agent integrations and initialize repository-local configuration
  2. /spec-kitty.charter — establish the project's governing principles
  3. /spec-kitty.specify — turn product intent into a mission specification under kitty-specs/
  4. /spec-kitty.plan — research the codebase and produce the implementation plan
  5. /spec-kitty.tasks — decompose the plan into acceptance-bound work packages and lifecycle lanes
  6. spec-kitty next --agent <agent> --mission <slug> — choose the next eligible action and dispatch implementation in an isolated worktree
  7. /spec-kitty.review and /spec-kitty.accept — review completed packages, record decisions, and validate the approved mission
  8. /spec-kitty.merge — merge accepted work to the target branch; a mission review and retrospective.yaml capture follow-up learning

Supported tools

Strengths

  • Repository-native governance preserves specs, plans, work packages, agent actions, review evidence, acceptance, and merge state as an auditable trail
  • Work-package boundaries, explicit lifecycle lanes, and isolated Git worktrees give parallel agents a concrete coordination model
  • Completes the post-planning loop that its Spec Kit ancestor historically left to the agent: next, review, acceptance, merge, and retrospective are first-class stages
  • Local-first operation does not require its optional hosted tracker or sync service, and the dashboard makes mission progress inspectable
  • Broad, explicitly documented integrations expose the same workflow across slash-command hosts and project-local skill hosts

Limitations

  • The project itself says the workflow is overkill for one-off edits, tiny scripts, and teams that do not use Git
  • Conventions are still moving quickly: the current documentation treats both the 1.x and 2.x lines as historical and requires migrations into 3.x
  • Its mission state, work-package lanes, worktrees, governance commands, dashboard, and retrospectives create substantially more ceremony than the Spec Kit workflow it extends
  • The Python CLI and its wide compatibility matrix add installation, upgrade, and host-parity maintenance that prompt-only frameworks avoid

Notes

Spec Kitty is a descendant, not an unrelated reinvention, of GitHub Spec Kit: its maintainer described it as “my fork” in a Spec Kit design discussion, and its current FAQ identifies the layer it adds — mission state, work-package lanes, worktree isolation, a dashboard, governance commands, and the explicit next → review → accept → merge runtime. That governed execution layer is the reason to track it separately. The supported-agents reference documents 16 host surfaces; the legacy Amazon Q surface is deliberately omitted above. This assessment observes the 3.x repository at f9fde44.

Added Aug 1, 2026 · Assessment last reviewed Aug 1, 2026 · How we track