Framework and Tool Snapshot — August 2026
Classification: Snapshot
Last technically verified: 2026-08-09
This appendix contains volatile information. Verify current documentation before adopting commands or integration claims.
| Framework | Character | Distinctive lesson | Deep coverage |
|---|---|---|---|
| GitHub Spec Kit | Governed artifact pipeline | Constitution, quality gates, analysis, implementation, convergence | Yes |
| OpenSpec/OPSX | Change- and delta-oriented | Evolve a brownfield system without losing current truth | Yes |
| BMAD | Product-to-delivery workflow | Progressive context, roles, readiness, and right-sized tracks | Yes |
| Kiro Specs | Requirements–design–tasks | IDE-centered structured delivery and steering | Survey |
| GSD | Context/execution discipline | Small plans, clean contexts, evidence-led completion | Survey |
| Spec Kitty | Isolated work packages | Worktree-oriented execution and merge governance | Survey |
| cc-sdd | Portable skill workflow | Cross-agent boundary and contract discipline | Survey |
| Reversa | Reverse specification | Explicit confidence and gaps for legacy recovery | Survey |
Capability-Based Selection
- Choose a lightweight repository-native workflow for small, well-understood changes.
- Choose OpenSpec when current-system truth and auditable deltas dominate.
- Choose Spec Kit when formal stages, extensibility, and convergence gates dominate.
- Choose BMAD when discovery, product planning, UX, architecture, and story delivery must form one workflow.
- Add isolated work packages when parallel agents would otherwise conflict.
The framework comparison is not a ranking. Team constraints and change risk decide the appropriate ceremony.