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
Decision gist · record as of 2026-05-21
Create Epics translates approved design documents into bounded architectural epics, one per module, ready for story breakdown. 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.
Use it when
- Create Epics maps each architectural module to a single bounded epic work unit.
- Create Epics defines epic scope with ADR coverage and requirement tracing.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
Donchitos/Claude-Code-Game-Studios/create-epics · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 1 file
.claude/skills/create-epics/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create epics from approved GDDs and architecture documents”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill transforms accepted architecture decision records into a single, layer-organized reference guide that tells programmers exactly what to do and what to avoid. It pulls rules from ADRs, technical preferences, and engine docs, then surfaces them by Foundation, Core, Feature, and Presentation layers—answering "what do I do?" faster than reading the reasoning behind each decision.
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
When a game design document is revised, architectural decisions built on it may become stale. This skill reads the changed GDD, compares it against all architecture decision records, and produces a detailed impact report classifying each ADR as still valid, needing review, or likely superseded. It then guides you through resolution decisions and updates your traceability index.
Create ADRs that capture the reasoning behind significant technical choices, including context, alternatives considered, and trade-offs. The skill guides you through gathering implementation details, identifying decision drivers, and structuring records that help future developers understand why architectural choices were made.
Obs Obsidian Bases lets you create database-like views within your Obsidian vault by defining .base files with filters, formulas, and multiple view types. Configure table, card, list, or map displays to organize and summarize your notes with computed properties and custom aggregations.
Adr helps you systematically capture architecture decisions with context, options, and consequences. Create numbered decision records, browse your decision history, and search past choices to avoid redundant deliberation.