gds-create-epics-and-stories

To turn game design requirements into actionable epics, consolidate your GDD, architecture notes, and UX inputs. This process maps functional requirements to standalone epics and details story-level acceptance criteria for development planning.

The best way to map functional requirements to epics is using a structured template that ensures FR coverage and traceability. Each epic remains standalone, value-driven, and integrates UX requirements where applicable.

You need GDD and architecture notes to generate agile stories effectively. The Skill consolidates these inputs with UX considerations to create a structured set of epics and stories ready for planning.

The epic approval workflow requires collaborative review to finalize epics before creating stories. This ensures epics driven by user value are explicitly approved, maintaining structure and consistency before story-level detailing begins.

Yes, you can integrate UX requirements into epics for comprehensive game planning. The consolidation process incorporates UX-DRs directly into applicable epics alongside architecture and GDD inputs.

Agile epics lack clear acceptance criteria and traceability when requirements are not explicitly mapped. Using template-driven documentation enforces structure, ensuring every FR is traced to an epic with detailed story-level acceptance criteria.