Create Epics

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 Epics" for me. It is the Game Studios epic author. At the standard and full tiers it loads the system GDDs (listed by the template's .claude/scripts/gdd-structure-check.sh), the master architecture document (missing means stop: module boundaries are never invented), the governing ADRs' status via adr-status.sh, the TR registry and, when present, the control manifest; at the minimal tier it works from design/game-brief.md alone and says first that the step is optional there. It then defines one epic per architectural module, layer by layer, showing each epic block and asking "Shall I create Epic: …?" one at a time — a yes covers only that epic — marks each requirement covered only when an Accepted ADR addresses it (untraced requirements are listed, with a warning at full), runs the producer PR-EPIC review from references/pr-epic-gate.md when the review gate says run, and writes each production/epics/[epic-slug]/EPIC.md plus its index row only after a separate write yes, guarded by the template's write-guard.sh so an existing EPIC.md is updated in place or skipped, never overwritten. The folder also holds CONTRACT.md, the handoff contract /create-stories relies on. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/create-epics/ 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-epics/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 a867fed460ac1ad49debf36302da1f1e44d0c9bc08aee2e14119fa09b572abd0 - CONTRACT.md: SHA-256 a48adfb04175d21ba016118e614c11def9477ad76c06ca26acf767d3ad4139b3 - references/pr-epic-gate.md: SHA-256 990efdfb2d6955ace5c3562e4753a5a8599f63cb39a48e51366124bcbca4f6d3 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: required inputs, output guarantees, immutability rules and hard constraints for the pipeline) and references/pr-epic-gate.md (the Phase 4 producer-review instructions, loaded only when the review gate runs). Nothing in the folder is a program; both companions are instructions 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, engine_values, system_overrides), runs the template's .claude/scripts/ helpers (gdd-structure-check.sh, adr-status.sh, md-section.sh, write-guard.sh), reads the template-produced architecture document, TR registry and control manifest, and can hand the epic set to the template's producer agent for the PR-EPIC review — files, scripts and an agent 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 works on my project's own GDDs and architecture docs, locally. - At use time it writes only in my own project and only after the per-epic yeses: each production/epics/[epic-slug]/EPIC.md and its row in production/epics/index.md, an existing EPIC.md being updated in place or skipped, never overwritten. It never writes story files. No account, key, payment or third-party service is named in the files I read. - Do not create any epic, do not run any template script, hook or agent, 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-epics folder into the agent's skills directory, in a folder named exactly "create-epics", keeping its 3 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: create-epics), 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 (it reads my GDDs and ADRs through the template's .claude/scripts helpers and resolves its settings through the template's yaml-helper hook), and that inside the template it writes each epic only after its own yes and never writes stories). 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.