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

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

View File

@@ -107,6 +107,16 @@ Present the categorized list, then route:
---
## Phase 3b: Creative Director Player Experience Review
After categorising findings, spawn `creative-director` via Task using gate **CD-PLAYTEST** (`.claude/docs/director-gates.md`).
Pass: the structured report content, game pillars and core fantasy (from `design/gdd/game-concept.md`), the specific hypothesis being tested.
Present the creative director's assessment before saving the report. If CONCERNS or REJECT, add a `## Creative Director Assessment` section to the report capturing the verdict and feedback. If APPROVE, note the approval in the report.
---
## Phase 4: Save Report
Ask: "May I write this playtest report to `production/qa/playtests/playtest-[date]-[tester].md`?"