skills.rest
claretagrapelike32
claretagrapelike32COMMUNITY
Explore all skills by this author →
GitHub

create-epics

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

Updated Aug 2, 2026
Search Tags:#game development#epic planning#production workflow#game design document#requirements registry#adr traceability#layer ordering
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill create-epics-claretagrapelike32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/create-epics
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill create-epics-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game production teams struggle to convert approved Game Design Documents and architecture decisions into actionable, bounded units of work. This Skill automates the translation of GDDs and ADRs into epics, one per architectural module, with full requirement traceability. ## 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, run the skill on the Core layer to generate EPIC.md files and an epics index, each listing governing ADRs, engine risk levels, and a definition of done. ## Quick Start Ask the AI to run create-epics for the foundation layer to generate epic files from the approved GDDs and architecture documents.

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 with a layer argument such as 'layer: foundation' or a specific system name. It reads in-scope GDDs, architecture docs, and ADRs, then presents each epic definition for approval before writing EPIC.md files.

What inputs are required before creating epics?▼

You need approved or designed GDDs, an architecture.md with module ownership, accepted ADRs, a control manifest, a TR registry, and engine version docs. The skill should run after create-control-manifest and architecture-review pass.

Does create-epics break work into stories?▼

No. The skill stops at the epic level and never creates stories. After each epic is written, you run the create-stories skill with the epic slug to break it into implementable stories.

What happens when requirements have no ADR coverage?▼

The skill warns about untraced TR-IDs before creating the epic. You can proceed with placeholders, skip the epic, or pause to write ADRs first; stories for untraced requirements are marked Blocked until ADRs exist.

When is the producer gate review skipped?▼

The PR-EPIC producer gate only runs in full review mode. In lean or solo modes it is skipped, and the skill proceeds directly to writing epic files after user approval.

Related Skills

Explore More Product & Management Skills→
scomofoscomofo

create-epics

Generate architectural epics from GDDs and technical architecture inputs.

Community
Advanced
dawn840705dawn840705

create-stories

Break down an epic into Markdown story files with metadata and acceptance criteria.

Community
Intermediate
ImaginerLabsImaginerLabs

bmad-check-implementation-readiness

Validate PRD, UX, Architecture, and Epics alignment before implementation.

Official
Advanced
rakhnianskii9rakhnianskii9

reverse-document

Generate design and architecture documents from existing code and prototypes.

Community
Advanced