create-epics

Translates approved GDDs and architecture documents into epics mapped to architectural modules.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-epics-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/create-epics
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-epics-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game production teams need to convert approved Game Design Documents and architecture decisions into structured, bounded units of work. This Skill automates the creation of epics—one per architectural module—with full traceability to ADRs and requirements, eliminating manual cross-referencing between design docs, architecture files, and requirement registries. ## Core Features & Use Cases - Layer-ordered epic generation: Processes systems in dependency-safe order (Foundation, Core, Feature, Presentation) based on the systems index. - ADR traceability checks: Maps TR-IDs from the requirements registry to Accepted ADRs and warns about untraced requirements before writing anything. - Producer gate review: In full review mode, spawns a producer subagent to validate epic scope against milestone timelines and team capacity before files are written. - Use Case: After architecture review passes for a Unity game project, run the skill on the Foundation layer to generate EPIC.md files and an epics index, each listing governing ADRs, engine risk levels, and requirement coverage. ## Quick Start Ask the AI to run create-epics for the foundation layer using the approved GDDs and architecture docs in this project.

Frequently Asked Questions about create-epics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create epics from a game design document?

Run the create-epics skill after your GDDs are approved and architecture review passes. It reads the systems index, maps each system to an architectural module, and writes an EPIC.md file per system with governing ADRs and requirement coverage.

What is the difference between an epic and a story in game production?

An epic defines what needs to be built and which architectural module owns it, mapping to one system from the GDD. Stories define implementation steps and are created separately by running create-stories for each epic.

When should I run create-epics in the production workflow?

Run it after create-control-manifest and architecture-review pass, once per layer as you approach that layer in development. Do not create Feature layer epics until Core is nearly complete, since the design will have changed.

What happens if requirements have no ADR coverage?

The skill warns about untraced TR-IDs before writing anything. The epic can still be created, but stories for those requirements are marked Blocked until ADRs exist, and you can pause to write ADRs first.

Does create-epics work in lean or solo review modes?

Yes. In lean and solo modes the producer structure gate (PR-EPIC) is skipped and epic files are written directly after user approval. Only full mode spawns the producer subagent to validate epic scope against timeline and capacity.