Pack candidate: speckit — spec-driven development pipeline

[arcaven]

Context

speckit (github/spec-kit) is a spec-driven development framework with 77k stars. It has a well-defined artifact model, clear directory structure, and Claude Code slash commands — making it a strong pack candidate.

Part of: #9 (SDD system survey)
Ref: kos finding-042

System Profile

• Repo: github/spec-kit
• Stars: 77k
• Fingerprint: .specify/ directory with init-options.json, templates/, extensions/, presets/
• Storage: Files (markdown)
• Pipeline: Linear — constitution → specify → plan → tasks → implement

Artifact Layout

.specify/
  init-options.json       # config + speckit_version field
  templates/              # spec document templates
  extensions/             # custom extensions
  presets/                # configuration presets
specs/
  <feature>/              # per-feature spec artifacts
.claude/
  commands/speckit/       # slash commands

What Sideshow Would Manage

1. Commands — .claude/commands/speckit/*.md (slash commands for the pipeline stages)
2. Templates — .specify/templates/ (spec document templates)
3. Extensions — .specify/extensions/ (custom extensions, if user-authored these stay local)
4. Presets — .specify/presets/ (configuration presets)

Version Detection

init-options.json contains a speckit_version field. Sideshow can read this for update detection and version-specific layout handling.

Implementation Notes

• speckit uses a .specify/ init directory + a specs/ output directory — sideshow manages the former, not the latter
• The slash commands follow the same .claude/commands/<pack>/ pattern as bmad and spectacle
• speckit's linear pipeline (constitution → specify → plan → tasks → implement) maps well to ordered slash commands
• Consider whether sideshow should manage init-options.json or treat it as user configuration that sideshow initializes but doesn't overwrite on update