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 FRs and NFRs, proposes a user-value-focused epic structure for approval, then generates stories with Given/When/Then acceptance criteria.

A GDD document is required, and an Architecture document is strongly recommended. A UX Design document is optional but treated as a first-class input, with its requirements extracted as separate UX-DR items that must be covered by stories.

Each story must be completable by a single dev agent and depend only on previously completed stories, never future ones. Database tables and entities are created only when a story needs them, avoiding large upfront setup stories.

Yes, the final validation step checks that every FR maps to at least one story, verifies epic independence, detects file churn across epics, and confirms all UX design requirements are covered before completing.

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