create-epics
Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug].
Donchitos · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Donchitos/Claude-Code-Game-Studios --skill create-epics技能说明
name: create-epics description: "Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug]." argument-hint: "[system-name | layer: foundation|core|feature|presentation | all] [--review full|lean|solo]" user-invocable: true allowed-tools: Read, Glob, Grep, Write, Agent, AskUserQuestion model: sonnet
!source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys review_mode,automation,workflow,docs.density,story_granularity,system_overrides
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
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
(at full). At standard, critical ADRs + a control manifest suffice. At
minimal, this skill is optional and not part of the path — /create-stories
synthesizes the epic from design/game-brief.md itself (Option A). If run anyway,
it decomposes directly from the brief with no GDD/ADR/manifest prerequisite.
At
minimal, this skill is optional —/create-storiessynthesizes the epic (Option A). At that tier/create-storiesreadsdesign/game-brief.mddirectly, writes a lightweight implicitproduction/epics/<slug>/EPIC.md, and generates stories from the MVP list — so the path is/brainstorm→/create-stories→/dev-story, with no separate/create-epicsor/sprint-planstep. Atstandard/fullan epic IS required:/create-storiesreadsproduction/epics/[slug]/EPIC.md, and skipping this skill there leaves/dev-storywith no story to implement — a dead end, not a shortcut.
1. Parse Arguments
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
workflow (per .claude/docs/workflow-modes.md):
create-epics runs project-wide: it uses the project-level tier for its
prerequisite expectations and consults
workflow_overrides.system_overrides.<system> per-system when reading each
in-scope GDD. See "Workflow tier adjustment" in Step 2.
story_granularity — it sizes the
epic's story breakdown: expect 3–5 child stories per epic at coarse, 5–10
at balanced (default), 10–20 at fine.
docs.density — it controls the depth of each epic's written scope and
rationale, not the story count (that is story_granularity). modes.rigor sets
it alongside workflow; set docs.density explicitly to vary epic prose alone:
terse = scope as bullets, one-line rationale; balanced = a scope paragraph
with light rationale (default); thorough = full scope prose with governing-ADR
rationale and risk discussion. The EPIC.md tables (GDD requirements, governing
ADRs) are structural and stay whole at every density.
Modes:
/create-epics all— process all systems in layer order/create-epics layer: foundation— Foundation layer only/create-epics layer: core— Core layer only/create-epics layer: feature— Feature layer only/create-epics layer: presentation— Presentation layer only/create-epics [system-name]— one specific system- No argument — ask: "Which layer or system would you like to create epics for?"
2. Load Inputs
Step 2a — Summary scan (fast, fail-open)
Establish the denominator first. Glob design/gdd/*.md, excluding the
non-system docs (game-concept.md, systems-index.md, game-pillars.md,
gameplay-tags.md, entity-registry.md, fixture-swap-ledger.md, and any
gdd-cross-review-*.md — the same set gdd-structure-check.sh skips). Call the
count N. If N is 0, there are no system GDDs — report "No system GDDs found
in design/gdd/ — run /design-system first" and stop.
Scan for Summary sections:
Grep pattern="^## Summary" glob="design/gdd/*.md" output_mode="content" -A 5
Interpret the M matches against N. These are three different outcomes, and a zero-match scan is never the same as "nothing in scope":
| Result | Meaning | Action |
|---|---|---|
| M = N | Every GDD has a Summary. | For layer:/[system-name] modes, use the Summary Quick-reference (Layer/Priority) to pick the in-scope set; skip full-reading the rest. |
| 0 < M < N | Partial adoption — older GDDs predate ## Summary. | Scope the M by their Summaries; determine the scope of the N − M unmatched from systems-index.md (layer/priority) and full-read those. |
| 0 matches, N > 0 | Expected for GDDs authored before /design-system emitted ## Summary. | Determine scope for all N from systems-index.md and full-read the in-scope set. This is the pre-optimization behaviour — correct, only more expensive. Note once: "No ## Summary sections found across [N] GDDs — scoping from systems-index.md instead of Summary." |
Never treat an absent ## Summary as an absent system. The scan narrows the
read set when it succeeds; it never shrinks the in-scope set. In all mode
every system is in scope regardless of Summary, so the scan is a convenienc