create-stories

Decomposing game development epics into implementation-ready stories involves reading an epic's EPIC.md, its GDD, governing ADRs, control manifest, and TR registry to break acceptance criteria into sized, traceable story files embedded with TR-IDs and QA test case templates.

Epic decomposition is the process of breaking large epics into small, developer-ready story files. It ensures traceability by embedding TR-IDs, ADR guidance, acceptance criteria, and manifest versions directly into each generated markdown story file.

To generate QA test cases and enforce ADRs when breaking down epics, the decomposition process enforces ADR existence, classifies story types, generates QA test case templates, and runs review-mode gates (solo/lean/full) before writing the markdown story files.

Using this epic decomposition process without a GDD is not recommended because the core logic reads the epic's GDD, governing ADRs, control manifest, and TR registry to decompose acceptance criteria into aligned, testable, and traceable story files.

The best way to automate story file creation from a game design document is to read the GDD alongside the epic's EPIC.md and ADRs, then generate production markdown story files that update the epic's Stories table for sprint planning.

Epic decomposition works with solo review modes as well as lean and full reviews. The process runs review-mode gates (solo/lean/full) to validate the generated story files before writing them to the production epics directory.