gds-create-epics-and-stories

Run this workflow with your GDD, Architecture, and optional UX Design documents in the planning artifacts folder. It extracts all requirements, proposes an epic structure for approval, then generates stories with acceptance criteria into an epics.md file.

A GDD containing functional and non-functional requirements and an Architecture document are required. A UX Design document is optional but treated as a first-class input whose requirements must also be covered by stories.

Each story uses the As a/I want/So that format with acceptance criteria in Given/When/Then structure. Criteria must be independently testable, reference specific requirements, and include edge cases and error conditions.

No. The workflow explicitly forbids forward dependencies. Each story must be completable using only the output of previous stories, and each epic must deliver standalone value without requiring later epics.

The final validation step checks every FR against the story breakdown and fails if any requirement lacks coverage. It also validates architecture compliance, story sizing, and file-churn patterns across epics before completion.