create-epics

You translate a game design document into technical epics by mapping approved design requirements to specific architectural modules and governing ADRs. This process defines bounded work scope, establishes ownership, and identifies engine-specific risks before development begins.

Requirement traceability validates game design document requirements against a technical registry before epic creation. This ensures all approved design features are systematically checked and prevents untraced requirements from entering the development pipeline.

You generate architectural epics from an approved GDD by operating across defined system layers to establish scope and engine risk profiles. This systematically bridges high-level design with technical implementation to produce clear, bounded work packages.

You need to assess engine risks for game development epics after finalizing your game design document and before breaking work into individual stories. Identifying engine-specific risks early ensures the technical team receives bounded work packages with clear architectural boundaries.

Yes, you can map system requirements to architectural modules directly before writing individual stories. The process maps requirements to specific modules and governing ADRs, validating requirement traceability against the technical registry before epic creation.

Automated epic generation from GDDs requires an approved game design document and a defined technical registry to function properly. It operates across defined system layers and cannot establish scope or validate requirements if architectural modules or ADRs are not previously defined.