gds-create-epics-and-stories

Provide your GDD, architecture, and optional UX design documents, then activate the workflow. It extracts all functional and non-functional requirements, proposes a user-value-focused epic structure for your approval, and generates stories with testable acceptance criteria.

It requires a GDD document and an architecture document, found in the planning artifacts folder as whole files or sharded folders with an index.md. A UX design document is optional but treated as a first-class input when present.

Each story uses the Given/When/Then format with independently testable criteria, including edge cases and error conditions. Stories follow the As a / I want / So that user story structure and reference the specific FRs they implement.

No. The workflow enforces a strict dependency rule: each story must be completable using only outputs from previous stories, and each epic must deliver standalone functionality without requiring future epics.

Yes. The final validation step checks every FR against the generated stories, verifies architecture compliance such as starter template setup, and confirms epics deliver user value rather than technical milestones.