create-epics

What problem does it solve?

Converts approved game design documents and architecture decisions into formal epics so product and engineering teams have clear, architect-owned scope without manual consolidation. It surfaces gaps in ADR coverage, assesses engine risk, and prevents premature story creation so work is scoped and traceable before implementation.

Core Features & Use Cases

• Epic generation from GDDs: Reads approved GDDs and maps each system to an architecture module to produce one epic per module.
• Governance & traceability checks: Cross-checks ADR coverage against the TR registry, reports untraced requirements, and summarizes governing ADRs and engine risk.
• Review gating and safe writes: Supports review modes (solo/lean/full), spawns a producer gate for full reviews, prompts for per-epic approval, and writes EPIC.md and an epics index only after confirmation.
• Use Case: A technical director runs this skill after architecture review to create a consistent set of epics for the next milestone and to highlight ADR work that must be completed first.

Quick Start

Run /create-epics layer: core --review lean to generate epics for all core systems after architecture and TR checks.