create-epics

To turn an approved GDD and architecture into epics, map systems to modules and apply governing ADRs to generate bounded epic files under the production directory. The process requires scanning in-scope GDDs and applying dependency-safe layer ordering.

Generating Godot project epics from architecture documents involves creating one bounded epic per system module, selecting governing accepted ADRs, and deriving engine risk to produce EPIC.md files under production/epics/.

You can trace untraced requirements when creating architectural epics because the process includes producer gate checks and explicit untraced requirement reporting to flag gaps needing attention before execution.

YAML frontmatter discovery is required to create epics from GDDs, as it enables in-scope GDD scanning and dependency-safe layer ordering to correctly transition architecture inputs into executable scope.

The next step after generating epics from GDD and architecture inputs is creating stories. The workflow produces EPIC.md files and updates index.md, then instructs you to run create-stories next.

You should not use automated epic generation from GDDs before completing control-manifest and architecture review, as the process requires approved technical architecture inputs and accepted ADRs to properly derive executable scope.