What problem does it solve?
It converts a large epic specification (GDD + governing ADRs + control manifest + TR registry) into a set of small, traceable, implementation-ready story documents that match acceptance criteria and architectural decisions.
Core Features & Use Cases
- Epic-to-story decomposition: Groups GDD acceptance criteria into focused stories with correct ordering (foundational first, edge cases last, UI last).
- Traceability by TR-IDs and ADR governance: Embeds the right TR requirement IDs and includes ADR decision summaries plus implementation guidance, stopping early if any governing ADR files are missing.
- Review and QA gating: Runs a QA lead readiness gate in full mode, then requires concrete automated test specs for Logic/Integration stories (manual verification steps for Visual/Feel/UI) before proceeding.
- Output organization: Writes
production/epics/[epic-slug]/story-NNN-[slug].md files and updates the epic’s EPIC.md stories table.
Quick Start
Use create-stories on a foundation epic by running /create-stories <epic-slug> to generate all story markdown files for that epic in production/epics/.