gds-create-epics-and-stories

Run this workflow after your GDD and Architecture documents exist in the planning artifacts folder. It extracts all functional and non-functional requirements, proposes a user-value-based epic structure for approval, then generates stories with acceptance criteria for each epic.

The workflow requires a GDD document and an Architecture document in the planning artifacts folder, supporting both whole files and sharded versions with an index.md. A UX Design document is optional but treated as a first-class input when present.

Each story uses the As a/I want/So that user story format followed by acceptance criteria in Given/When/Then structure. Criteria are written to be independently testable and reference the specific GDD requirements they fulfill.

Yes, the final validation step checks that every FR maps to at least one story, verifies epic independence, confirms stories have no forward dependencies, and flags file churn across epics. The workflow does not complete until all validations pass.

Yes, the customize.toml file supports team and user-level overrides for activation steps, persistent facts, and post-completion behavior. Overrides merge using structural rules where scalars override and arrays append.