Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

create-stories

Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.

HYClub · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add HYClub/deepseek-harness-game-studios --skill create-stories

About this skill


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 at standard/full: "No epic at production/epics/[slug]/EPIC.md. Run /create-epics to create it, or check the slug with ls production/epics/." Do not decompose from a guess. At minimal there are no /create-epics epics to name and that skill is not on the path — say so, take Step 2's minimal branch, and name the slug it uses.

  • No argument — at minimal there are no epics yet (Option A): skip to Step 2's minimal branch and synthesize the epic from design/game-brief.md. At standard/full, ask "Which epic would you like to break into stories?" and Glob production/epics/*/EPIC.md to 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 under production/epics/. Run /create-epics layer: foundation first — an epic is what this skill decomposes."

    The zero-epic path is load-bearing. Asking which epic and globbing to list them leaves an AskUserQuestion with nothing to offer when the glob is empty. Route to /create-epics instead — 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 minimal this does not apply: there are deliberately no epics, and the branch above synthesizes one from the brief.


2. Load Everything for This Epic

minimal tier — synthesize the epic from the brief (Option A). At minimal there is no /create-epics step and usually no EPIC.md. Instead: 0. No design/game-brief.md? Stop: "There is no brief to build stories from yet — run /brainstorm first; it writes the one-page brief." An EPIC.md already at production/epics/<slug>/ — the named epic, or the brief-title slug (/create-epics run 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 update EPIC.md. Stories already in production/epics/<slug>/? This is a return visit — /help sends a finished build order back here. Never rewrite an existing `sto

Read the complete source ↗