create-epics

Creating epics from a game design document involves mapping approved design docs and system architecture to bounded, module-aligned work units. This skill generates epics with clear ownership, governing architecture decision records, and engine risk assessments.

Requirement tracing in game development epics flags untraced requirements lacking governing architecture decision records. This prevents unplanned work by ensuring all design inputs are accounted for prior to story breakdown.

You need to generate epics for game architecture layers immediately after architecture review is complete and the game design document is approved. This scopes work per system module across foundation, core, feature, and presentation layers.

To structure trackable epics for a game project, you define clear ownership, governing architecture decision records, engine risk assessments, and untraced requirement flags for each epic. This ensures module-aligned work prior to story breakdown.

Yes, you can generate epics for specific game modules like combat and inventory by mapping each architectural module to a defined epic. This applies to game projects organized by foundation, core, feature, and presentation architectural layers.

Untraced requirements are flagged during epic creation to prevent unplanned work and ensure all design inputs are accounted for. This happens prior to story breakdown when requirements lack governing architecture decision records.