ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 13:01:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Split /create-epics-stories into /create-epics + /create-stories; add /dev-story

Browse Source 
- NEW /create-epics (agent: technical-director): architect-level epic scoping,
  one epic per architectural module. Does not create stories.
- NEW /create-stories (agent: lead-programmer): decomposes a single epic into
  story files with embedded TR-IDs, ADR guidance, and test evidence paths.
- NEW /dev-story: the missing implementation skill — reads a story, loads full
  context (TR registry, ADR, control manifest, engine prefs), routes to the
  correct programmer agent via Task, and drives implementation to completion
  including writing the test.
- DEPRECATED /create-epics-stories: added redirect notice; original content
  preserved for reference.
- Updated /gate-check: Pre-Prod→Production artifact check and follow-up actions
  now reference the two new skills.
- Updated workflow-catalog.yaml: replaced create-epics-stories step with two
  separate steps; implement step now references /dev-story with command field.

Story loop is now explicit:
  /story-readiness → /dev-story → /code-review → /story-done

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-16 14:57:39 +11:00
parent db416aa494
commit 4ca6500a21
6 changed files with 723 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.claude/skills/create-epics-stories/SKILL.md
View File

@@ -1,6 +1,6 @@
---
name: create-epics-stories
description: "Translate approved GDDs + architecture + ADRs into implementable epics and stories. Each story embeds the GDD requirement it satisfies, the ADR governing implementation, acceptance criteria, engine compatibility notes, and control manifest rules. Programmers need nothing else to implement a story correctly."
description: "DEPRECATED — use /create-epics then /create-stories instead. This skill has been split into two focused skills: /create-epics (architect-level scoping, one per layer) and /create-stories (lead-programmer story breakdown, one per epic)."
argument-hint: "[system-name | layer: foundation|core|feature|presentation | all]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Write, Task
@@ -8,7 +8,22 @@ context: fork
agent: technical-director
---
# Create Epics & Stories
# Create Epics & Stories — DEPRECATED
> **This skill has been superseded.** Use the two-skill workflow instead:
>
> 1. `/create-epics layer: foundation` — define Foundation epics (technical-director)
> 2. `/create-stories [epic-slug]` — break each epic into stories (lead-programmer)
> 3. `/create-epics layer: core` — define Core epics
> 4. `/create-stories [epic-slug]` — break each Core epic into stories
>
> **Why the split?** Epics are architectural scope decisions (technical-director's domain).
> Stories are implementation decomposition (lead-programmer's domain). Mixing them in one
> skill caused the wrong agent to own the wrong decisions.
>
> **To implement a story** once stories exist, use `/dev-story [story-path]`.
---
This skill translates the approved design and architecture into implementable
work units. Each **epic** maps to one architectural module. Each **story** is a