create-epics

To translate architecture into trackable epics, this Skill maps each architectural module to a bounded epic, capturing scope, governing ADRs, and engine risk assessments. It processes approved GDDs in layer order and writes EPIC.md files.

You can generate epics for every system in layer order by running the generation command for all modules. This applies layer-based processing to your approved GDDs and creates bounded epics for each architectural component.

When creating epics from architecture, untraced requirements are flagged automatically. The system surfaces these governance gaps and prompts for ADR creation before proceeding to ensure full traceability.

Yes, this epic generation process links each module to its governing ADRs and engine risk assessments. It surfaces governance data during translation to ensure clear ownership and traceability across the architecture.

You need to update the production epic index after architecture translation once the generated epics are approved. The system automatically updates this index and writes the corresponding EPIC.md files to the production directory.

The best way to ensure clear ownership and traceability when breaking down architecture into epics is to map each module to a bounded epic with explicit ADR governance. Flagging untraced requirements before approval ensures no architectural decisions are missed.