create-stories
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.
HYClub · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add HYClub/deepseek-harness-game-studios --skill create-stories技能说明
name: create-stories description: "Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics." argument-hint: "[epic-slug | epic-path] [--review full|lean|solo]" user-invocable: true allowed-tools: Read, Glob, Grep, Write, Edit, Agent, AskUserQuestion, Bash(bash "*/.claude/skills/create-stories/../../hooks/yaml-helper.sh" resolve_config *) model: sonnet
!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.
Create Stories
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)
1. Parse Argument
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
covering one task at balanced (rigor: standard), 1 AC at fine (the story name is
the AC restatement). Group or split ACs into stories to hit the target.
docs.density — it controls the depth of each story's prose (context,
implementation notes, ADR summary), not the AC count (that is
story_granularity) and never the AC text itself. modes.rigor sets it
alongside workflow; set docs.density explicitly to vary story prose alone:
terse (the default, via rigor: minimal) = notes as bullets, no preamble; balanced = short context paragraph +
notes (rigor: standard); thorough = full context, implementation guidance, and ADR
rationale. The embedded TR-ID reference, ADR Version stamp, and acceptance
criteria are structural and are never trimmed by density.
-
/create-stories [epic-slug]— e.g./create-stories combat -
/create-stories production/epics/combat/EPIC.md— full path also accepted -
A named epic that does not exist — if
production/epics/[slug]/EPIC.md(or the given path) is missing, stop atstandard/full: "No epic atproduction/epics/[slug]/EPIC.md. Run/create-epicsto create it, or check the slug withls production/epics/." Do not decompose from a guess. Atminimalthere are no/create-epicsepics to name and that skill is not on the path — say so, take Step 2'sminimalbranch, and name the slug it uses. -
No argument — at
minimalthere are no epics yet (Option A): skip to Step 2'sminimalbranch and synthesize the epic fromdesign/game-brief.md. Atstandard/full, ask "Which epic would you like to break into stories?" and Globproduction/epics/*/EPIC.mdto list available epics with their status.If that glob returns nothing at
standard/full, stop — do not build a question with no options. Report: "No epics found underproduction/epics/. Run/create-epics layer: foundationfirst — an epic is what this skill decomposes."The zero-epic path is load-bearing. Asking which epic and globbing to list them leaves an
AskUserQuestionwith nothing to offer when the glob is empty. Route to/create-epicsinstead — it is named as Previous step in this skill's own header.Note what this skill guarded and what it did not. Step 2's ADR validation is thorough: three tiers, each with its own stop condition, and an explicit message naming the missing file. That is the deepest input. The first input — does an epic exist at all — went unchecked. Guarding the far end of a chain while leaving the near end open is the shape to watch for.
At
minimalthis does not apply: there are deliberately no epics, and the branch above synthesizes one from the brief.
2. Load Everything for This Epic
阅读完整来源 ↗
minimaltier — synthesize the epic from the brief (Option A). Atminimalthere is no/create-epicsstep and usually noEPIC.md. Instead: 0. Nodesign/game-brief.md? Stop: "There is no brief to build stories from yet — run/brainstormfirst; it writes the one-page brief." AnEPIC.mdalready atproduction/epics/<slug>/— the named epic, or the brief-title slug (/create-epicsrun anyway, or an earlier run of this skill) — is the epic: use its scope, still traced to the brief, and never rewrite it; Step 6 only appends its Stories table, and the Step 5 ask says updateEPIC.md. Stories already inproduction/epics/<slug>/? This is a return visit —/helpsends a finished build order back here. Never rewrite an existing `sto