Create Stories

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Create Stories" for me. It breaks one epic into implementable stories with acceptance criteria, run once per epic in dependency order (Foundation, Core, Feature, Presentation). At the standard and full tiers it loads the epic's EPIC.md, extracts GDD sections, the control manifest's layer rules and the TR registry entries with the template's .claude/scripts/ helpers (md-section.sh, adr-status.sh), reports every governing ADR's status, types each story (Logic, Integration, Visual/Feel, UI or Config/Data), marks stories governed by a Proposed, Deprecated or Superseded ADR as Blocked, proposes t-shirt estimates, and — only in full review mode — runs a QA-lead gate through references/qa-lead-gate.md. At the minimal tier it builds the epic from the one-page design/game-brief.md instead, with no GDD, ADR or registry reads. It presents the full story list and asks once before writing anything, then writes production/epics/[epic-slug]/story-NNN-[slug].md files, the EPIC.md Stories table and the epics index row; it never rewrites an existing story, never reuses a story number, and never starts implementation. Its folder also holds CONTRACT.md, the handoff contract for the story files it produces. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/create-stories/ folder at the pinned commit: 3 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/create-stories/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - CONTRACT.md: SHA-256 7ab7c94960b73477bbd2620e986d7c6c1b7046e7cecfe48aa10e7f420d117b5e - SKILL.md: SHA-256 6fbbc16b580e90cf219e1bc67aaebeaf5e81e0dbc24c3b419d493dc6362282c3 - references/qa-lead-gate.md: SHA-256 752d3bc7d4d5de0fa36031821d00128d5c7eb3f3bf66fd6f9e869e943e51eb98 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 3 files: SKILL.md, CONTRACT.md (the handoff contract describing the story files, their guaranteed fields and the immutability rules) and references/qa-lead-gate.md (the QA-lead review loaded only when the resolved review gate says skill-gates=run). Nothing in the folder is a program; all three are instructions or contract text the skill reads at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, review_gate, automation, workflow, docs.density, story_granularity, qa.level, system_overrides) and calls template scripts under .claude/scripts/ (adr-status.sh, md-section.sh) — files that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Inside the template it reads my project's EPIC.md, GDDs, ADRs, control manifest and TR registry locally. - At use time it writes only after one explicit ask that names every file: the story files under production/epics/[epic-slug]/, the EPIC.md Stories table, and the epic's row in production/epics/index.md when that index exists. It never rewrites an existing story file and never starts implementing code. No third-party service, account or credential is named in the files I read. - Do not create any story, do not run any template hook or script, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole create-stories folder into the agent's skills directory, in a folder named exactly "create-stories", keeping its 3 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: create-stories), the 3 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone — that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook and calls the template's .claude/scripts helpers), and that inside the template it breaks one epic into story files under production/epics/ only after showing the full list and asking once). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.