create-epics

To generate architecture epics from an approved GDD, you parse the GDD summary and map architectural module ownership into bounded epics per system and layer. This process applies ADR governance and requirement traceability to ensure clear ownership before implementation.

Requirements traceability in epic generation uses the TR registry to map accepted ADRs to specific requirements. It identifies which requirements are covered and flags untraced gaps as blocked until governing ADRs are established.

You scope epic generation to a specific architectural layer by passing a layer argument during execution, such as specifying foundation. The system then loads full GDD context only for in-scope systems and generates epics in dependency-safe order across foundation, core, feature, and presentation layers.

Yes, you can skip collaboration gates when generating epics in a solo workflow by using solo or lean modes. These modes bypass the producer PR-EPIC gate and per-epic definition approval steps to streamline the orchestration process.

ADR governance surfaces engine risk by identifying governing Architectural Decision Records for each epic, summarizing their decisions, and deriving the overall engine risk from the highest-risk ADR. This ensures development governance highlights critical technical constraints.

After writing EPIC markdown files and updating the epics index, you should run the create-stories command with the specific epic-slug. This next step converts the scoped architecture epics into actionable implementation stories.