create-epics

To convert game design documents into development epics, this Skill transforms approved design documents and architecture decisions into bounded epics aligned with architectural modules across Foundation, Core, Feature, and Presentation layers. It requires requirement-to-ADR traceability before generating standardized epic documentation.

Planning game production epics after architecture review involves mapping requirements to governing ADRs, identifying untraced requirements, and recording engine risk. This Skill applies dependency-safe ordering and approval checkpoints to define scope and definition of done across eligible layers.

Yes, creating game development epics requires approved architecture decisions and a control-manifest approval. This Skill needs requirement-to-ADR traceability and engine-risk assessment inputs to ensure epic scoping aligns properly with architectural modules.

No, this Skill creates standardized epic documentation and index outputs without creating stories. It focuses on defining bounded epics, ADR coverage, and dependency-safe ordering, stopping before story-level planning begins.

Requirement-to-ADR traceability in epic planning maps each requirement to its governing Architecture Decision Records. This Skill identifies untraced requirements and records engine risk to ensure every bounded epic aligns with approved architectural decisions across the Foundation, Core, Feature, and Presentation layers.

Automated epic planning for game production is limited to post-architecture review phases and requires control-manifest approval. It does not create user stories and depends entirely on receiving approved game design documents and complete architecture decisions as inputs.