Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Passed 10 of 17 test cases with the skill, and 6 of 17 without it.
and 5 more in the full report
5 fixed8 passed either way10 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/13/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
During story generation for a non-critical feature epic under standard tier, we discover that governing ADR-0015 is missing from disk. Should processing halt immediately, or proceed with warnings?
| Checked | Without skill | With skill |
|---|---|---|
| Issues a warning for missing non-critical decisions under standard tier. | Missed | Passed |
| Marks the generated story as Blocked until the decision file exists. | 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,qa.level,system_overrides
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
A story is a single implementable behaviour — small enough to complete in one focused session, self-contained, and fully traceable to a GDD requirement and an ADR decision. Stories are what developers pick up. Epics are what architects define.
Run this skill per epic, not per layer. Run it for Foundation epics first, then Core, and so on — matching the dependency order.
Output: production/epics/[epic-slug]/story-NNN-[slug].md files
Previous step: /create-epics [system]
Next step after stories exist: /story-readiness [story-path] then /dev-story [story-path] —
at workflow: minimal, /dev-story [story-path] directly (/story-readiness is not on the minimal path)
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 for this epic's system (per .claude/docs/workflow-modes.md) —
use the system_overrides row for <system> if the block lists one, else the
project value. <system> is the epic slug / its GDD system. The tier sets which prerequisites block — see the note in Step 2.
story_granularity — it sets each
story's AC load: 5–10 ACs covering a whole feature at coarse (the default, via rigor: minimal), **2–4 ACs
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.