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

Add director gates system: shared review checkpoints across all workflow skills

Browse Source 
Creates .claude/docs/director-gates.md as a central registry of 18 named gate
prompts (CD-*, TD-*, PR-*, LP-*, QL-*, ND-*, AD-*) covering all 7 production
stages. Skills now reference gate IDs instead of embedding inline director prompts,
eliminating drift when prompts need updating.

Updated 15 skills to use gate IDs: brainstorm, map-systems, design-system,
architecture-decision, create-architecture, create-epics, create-stories,
sprint-plan, milestone-review, playtest-report, prototype, story-done,
gate-check, setup-engine, start.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-29 17:24:06 +11:00
parent 167fb6c5f2
commit b139bcf087
16 changed files with 997 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
.claude/skills/create-architecture/SKILL.md
View File

@@ -325,6 +325,37 @@ derived from the game concept, GDDs, and technical preferences]
---
## Phase 7b: Technical Director Sign-Off + Lead Programmer Feasibility Review
After writing the master architecture document, perform an explicit sign-off before handoff.
**Step 1 — Technical Director self-review** (this skill runs as technical-director):
Apply gate **TD-ARCHITECTURE** (`.claude/docs/director-gates.md`) as a self-review. Check all four criteria from that gate definition against the completed document.
**Step 2 — Spawn `lead-programmer` via Task using gate LP-FEASIBILITY (`.claude/docs/director-gates.md`):**
Pass: architecture document path, technical requirements baseline summary, ADR list.
**Step 3 — Present both assessments to the user:**
Show the Technical Director assessment and Lead Programmer verdict side by side.
Use `AskUserQuestion` — "Technical Director and Lead Programmer have reviewed the architecture. How would you like to proceed?"
Options: `Accept — proceed to handoff` / `Revise flagged items first` / `Discuss specific concerns`
**Step 4 — Record sign-off in the architecture document:**
Update the Document Status section:
```
- Technical Director Sign-Off: [date] — APPROVED / APPROVED WITH CONDITIONS
- Lead Programmer Feasibility: FEASIBLE / CONCERNS ACCEPTED / REVISED
```
Ask: "May I update the Document Status section in `docs/architecture/architecture.md` with the sign-off?"
---
## Phase 8: Handoff
After writing the document, provide a clear handoff: