create-epics

To translate architecture decisions into development epics, map in-scope systems to architectural modules and link governing ADRs to generate bounded epic scopes. This ensures engineering teams have clear ownership boundaries and traced ADR coverage before building.

Scoping epics using Architecture Decision Records involves mapping systems to architecture modules and identifying governing ADRs to define boundaries. This approach surfaces engine risks derived from ADRs and warns about untraced requirements during epic creation.

Tracing requirements from a GDD to production epics requires loading only in-scope GDDs and ADRs, mapping them to architectural modules, and flagging untraced TR requirements. The process writes EPIC.md files only after verifying coverage during the PR-EPIC gate.

Yes, a control-manifest and architecture review must pass before generating epics. The workflow enforces review modes and requires PR-EPIC phase gate approval before proposing each epic one-by-one and writing to production/epics.

You should not use automated epic generation if your workflow lacks approved GDDs, governing ADRs, or a control-manifest review. The process requires resolving review mode and loading in-scope architecture data to properly map systems and enforce the PR-EPIC gate.

Yes, you can generate epics layer-by-layer across foundation, core, feature, and presentation tiers. The workflow progresses from architecture review into layer-by-layer discovery-to-production planning, creating one epic for each architectural module within the selected layer.