What problem does it solve?
It converts a single large epic into smaller, traceable story files so developers can implement work in focused, GDD/ADR-aligned sessions with clear acceptance criteria and QA evidence paths.
Core Features & Use Cases
- Epic-to-stories decomposition: Reads the epic overview, the epic’s GDD, governing ADRs, and the control manifest, then generates story files in the required
production/epics/[epic-slug]/ structure.
- Traceability by design: Each story embeds the specific GDD requirement TR-ID, links to governing ADR guidance, and includes acceptance criteria and test evidence expectations.
- Gate-based readiness workflow: Applies review-mode rules and spawns a QA lead readiness gate before writing story files, with blocked/proposed ADR handling.
- Outputs for the next step: Prepares stories for downstream
/story-readiness and /dev-story execution without starting implementation.
Quick Start
Run create-stories for the epic “combat” by issuing the command: /create-stories combat.