create-epics

To break a game design document (GDD) into actionable epics, you automate the translation of approved GDDs and architecture into executable epics for each architectural module. This ensures alignment with ADRs and governance.

Generating per-system epics across Foundation, Core, Feature, and Presentation layers requires enforcing a layer-aware workflow. You run commands specifying the layer to generate epics for all systems within that architectural layer.

Tracking untraced requirements when creating epics from approved GDDs happens automatically during epic generation. The process surfaces untraced requirements while documenting epic scope for downstream story creation.

Approved architecture decision records (ADRs) are considered during epic generation to ensure alignment. ADR governance is applied to the process, validating that the generated epics for each architectural module comply with established decisions.

Yes, you can use this epic generation process to prepare for downstream story creation. It documents the epic scope and outputs a clear Next Step instruction to run the create-stories command for the generated epic slug.

You should not use automated epic generation from GDDs if your architectural modules lack approved governance or ADRs. The process relies on translating approved GDDs and architectural guidance into well-scoped epics.