create-epics
Create Epics transforms approved design documents and architecture into named, bounded epics—one per architectural module. Each epic defines scope, identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage. Run this skill once per development layer after control manifest and architecture review pass; follow each epic with /create-stories to decompose into implementable work.
Create Epics translates approved design documents into bounded architectural epics, one per module, ready for story breakdown.
AI-generated summary based on this skill's SKILL.md
Install
Donchitos/Claude-Code-Game-Studios/create-epics · repository language: Shell
git clone https://github.com/Donchitos/Claude-Code-Game-Studios
cp -r Claude-Code-Game-Studios/.claude/skills/create-epics ~/.claude/skills/create-epicsnpx skillfed install Donchitos/Claude-Code-Game-Studios/create-epicsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create epics from GDD and architecture documents?
Create Epics transforms approved design documents and architecture into named, bounded epics—one per architectural module. Each epic defines scope, identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage. Run this skill once per development layer after control manifest and architecture review pass.
How does Create Epics map architectural modules to bounded work?
Create Epics maps each architectural module to a single bounded epic work unit. The skill organizes epics by architectural layer (Foundation, Core, Feature, Presentation), ensuring each module's scope aligns with its layer's responsibilities and dependencies.
What does epic scope definition include in Create Epics?
Create Epics defines epic scope with ADR coverage and requirement tracing. Each epic identifies governing architecture decisions, flags engine risk, and traces requirements to decision coverage, ensuring full traceability before story creation begins.
How to define epics per architectural layer using Create Epics?
Create Epics generates epics organized by architectural layer: Foundation, Core, Feature, and Presentation. Each layer receives its own set of bounded epics that respect layer boundaries and architectural dependencies.
What gaps does Create Epics identify before story creation?
Create Epics identifies untraced requirements and ADR gaps before story creation. The skill flags missing decision coverage and requirement traceability so gaps are resolved at epic scope rather than during implementation.
When should I run Create Epics in my development workflow?
Run Create Epics once per development layer after control manifest and architecture review pass. Follow each epic with /create-stories to decompose the bounded epic into implementable work.
SKILL.md
rendered from the published skill — quoted content, verbatim
Create Epics
An epic is a named, bounded body of work that maps to one architectural module. It defines what needs to be built and who owns it architecturally. It does not prescribe implementation steps — that is the job of stories.
Run this skill once per layer as you approach that layer in development. Do not create Feature layer epics until Core is nearly complete — the design will have changed.
Output: production/epics/[epic-slug]/EPIC.md + production/epics/index.md
Next step after each epic: /create-stories [epic-slug]
When to run: After /create-control-manifest and /architecture-review pass.
1. Parse
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/create-epics/SKILL.md