Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/create-epics
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Passed 10 of 16 test cases with the skill, and 2 of 16 without it.
and 12 more in the full report
11 fixed3 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are defining epics under review_mode=solo. Is the producer gate PR-EPIC spawned before writing epic files?
| Checked | Without skill | With skill |
|---|---|---|
| Skips spawning the producer gate under solo review mode. | Missed | Passed |
| Proceeds toward file writing after solo confirmation. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" 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.
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 suffice, and a control manifest is
read if present. 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.
test cases passed, vs 2 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.