create-epics

To convert an approved Game Design Document (GDD) into executable Epics, you supply the system name and optional layer. The tool generates a production-ready EPIC.md file defining functional modules, architecture decisions, and engine risks for downstream story creation.

Structuring Epics from architecture decisions involves mapping each system across Foundation, Core, Feature, and Presentation layers. This approach links ADRs and TR statuses directly to the Epic, ensuring traceability and clear scope boundaries to prevent feature creep.

You trace ADR governance and engine risks by referencing the GDD path, ADR list, and risk notes during Epic generation. The resulting Epic scaffold explicitly links these governance elements, providing auditability and accountability for untracked requirements.

Yes, you can generate Epics for Foundation, Core, Feature, and Presentation layers. By supplying the system name and specifying the optional layer, the tool maps each system to the appropriate architectural layer within the EPIC.md output.

Yes, an approved GDD and governance ADRs are required prerequisites. Epic generation transforms these approved design documents and architecture decisions into a scalable Epic structure, preparing the ground for controlled downstream story creation.

Defining scope boundaries and untracked requirements during Epic generation prevents feature creep and scope drift. It clearly establishes project limits within the EPIC.md, ensuring controlled and focused downstream story creation.