create-epics

To create epics from GDDs and ADRs, you automate the transformation of approved design documents into bounded epics per architectural module. This process maps each system to a module and validates ADR coverage, engine risk, and traced requirements before generating the epics.

Mapping architectural modules to epics in dependency order involves processing Foundation, Core, Feature, and Presentation layers sequentially. Each system is mapped to its corresponding module, ensuring governing ADRs validate requirements and surface any untraced items before epic creation.

No, creating epics from ADRs does not break them down into user stories. The epic creation process defines scope, governing ADRs, engine risk, and untraced requirements, but requires a separate downstream step to generate stories from the created epic.

Validating ADR coverage and engine risk before epic creation involves ensuring architecture decision records govern the relevant GDD requirements. The transformation process automatically surfaces untraced items and assesses engine risk for each architectural module prior to generating the epic.

Yes, you can generate epics for every system in an architectural layer at once by running an automated transformation across all systems. This processes the Foundation, Core, Feature, or Presentation layers in dependency order to produce the relevant bounded epics.