create-epics

To turn approved architecture and GDD modules into structured epics, map each architectural module to an epic defining scope, governing ADRs, engine risk, and untraced requirements. The workflow gates creation with producer epics and gate-check steps before generating per-epic files.

Ensuring ADR coverage aligns with traceability requirements involves mapping approved GDDs to epics and verifying that governing ADRs cover all TR requirements. The process surfaces untraced requirements and documents engine risk per epic during creation.

Start the epic creation workflow by providing the initial epic for the first in-scope system. The process then applies epics to architectural modules across layers, generating production EPIC.md files and updating the epics index.

No, this epic creation process does not split epics into user stories. It strictly enforces that no stories are created; you must use a separate story creation step after each epic is fully generated and validated.

No, you cannot generate epics directly without approved GDDs. The creation process requires validated GDDs and architectural boundaries as input, gating epic creation with producer epics and gate-check steps before any production files are written.

Untraced requirements and engine risk are documented during epic mapping to surface gaps between approved GDDs and architectural modules. This ensures governing ADR coverage aligns with TR requirements and highlights potential engine vulnerabilities before downstream story creation.