完善 brainstorm 支柱文档与审查强度规则

references/studio-docs/director-gates.md

@@ -32,8 +32,14 @@ profile text into a generic default agent.
 
 ## Review Modes
 
-Review intensity controls whether director gates run. It can be set globally
-(persists across sessions) or overridden per skill run.
+Review intensity controls whether director and lead **review gates** run. It is
+not a global switch for all custom-agent or subagent usage: a future team
+workflow may still call specialist agents as part of its core work. Apply
+review mode only to gate invocations such as `CD-PILLARS`, `TD-FEASIBILITY`,
+`PR-SCOPE`, and the `*-PHASE-GATE` checks.
+
+Review intensity can be set globally (persists across sessions) or overridden
+per skill run.
 
 **Global config**: `production/review-mode.txt` — one word: `full`, `lean`, or `solo`.
 Set once during `/start`. Edit the file directly to change it at any time.
@@ -45,14 +51,14 @@ Examples:
 ```
 /brainstorm space horror           → uses global mode
 /brainstorm space horror --review full   → forces full mode this run
-/architecture-decision --review solo     → skips all gates this run
+/architecture-decision --review solo     → skips review gates this run
 ```
 
 | Mode | What runs | Best for |
 |------|-----------|----------|
-| `full` | All gates active — every workflow step reviewed | Teams, learning users, or when you want thorough director feedback at every step |
-| `lean` | PHASE-GATEs only (`/gate-check`) — per-skill gates skipped | **Default** — solo devs and small teams; directors review at milestones only |
-| `solo` | No director gates anywhere | Game jams, prototypes, maximum speed |
+| `full` | All key director / lead review gates call their custom agents | Teams, learning users, or when you want thorough director feedback at every step |
+| `lean` | Only PHASE-GATE review gates such as `/gate-check` call directors; ordinary per-skill review gates are skipped | **Default** — solo devs and small teams; directors review at milestones only |
+| `solo` | All director review gates are skipped | Game jams, prototypes, maximum speed |
 
 **Check pattern — apply before every gate spawn:**
 
@@ -63,8 +69,9 @@ Before spawning gate [GATE-ID]:
 3. Else default to lean
 
 Apply the resolved mode:
-- solo → skip all gates. Note: "[GATE-ID] skipped — Solo mode"
-- lean → skip unless this is a PHASE-GATE (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)
+- solo → skip all director / lead review gates. Note: "[GATE-ID] skipped — Solo mode"
+- lean → skip ordinary per-skill review gates; only run PHASE-GATE checks
+         (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)
          Note: "[GATE-ID] skipped — Lean mode"
 - full → spawn as normal
 ```
@@ -79,9 +86,12 @@ Apply the resolved mode:
 3. Else default to `lean`
 
 Apply the resolved mode:
-- `solo` → **skip all gates**. Note in output: `[GATE-ID] skipped — Solo mode`
-- `lean` → **skip unless this is a PHASE-GATE** (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE). Note: `[GATE-ID] skipped — Lean mode`
-- `full` → spawn as normal
+- `full` → **spawn all key director / lead review gates** as described by the skill.
+- `lean` → **spawn only PHASE-GATE review gates** such as `/gate-check`
+  (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE). Skip ordinary
+  per-skill review gates and note: `[GATE-ID] skipped — Lean mode`
+- `solo` → **skip all director review gates**. Note in output:
+  `[GATE-ID] skipped — Solo mode`
 
 ```
 # Apply mode check, then:
@@ -146,8 +156,15 @@ or any time pillars are revised)
 **Context to pass**:
 - Full pillar set with names, definitions, and design tests
 - Anti-pillars list
+- Pillar conflict priority
 - Core fantasy statement
 - Unique hook ("Like X, AND ALSO Y")
+- Required output document path for `/brainstorm`: `design/gdd/game-pillars.md`
+- Template to use when the document is created or updated:
+  `references/studio-docs/templates/game-pillars.md`
+- Existing `design/gdd/game-pillars.md` contents, if the file already exists
+- Orchestrator assessment: missing / present and current / present but stale /
+  present but incomplete
 
 **Prompt**:
 > "Review these game pillars. Are they falsifiable — could a real design decision
@@ -155,7 +172,18 @@ or any time pillars are revised)
 > they differentiate this game from its closest comparables? Would they help resolve
 > a design disagreement in practice, or are they too vague to be useful? Return
 > specific feedback for each pillar and an overall verdict: APPROVE (strong), CONCERNS
-> [list] (needs sharpening), or REJECT (weak — pillars do not carry weight)."
+> [list] (needs sharpening), or REJECT (weak — pillars do not carry weight).
+> When this gate is invoked from `/brainstorm` after the user has locked pillars,
+> ensure `design/gdd/game-pillars.md` exists as the brainstorm-stage pillar
+> source of truth. If it already exists and matches the locked pillars, review it
+> in place and avoid rewriting for churn. If it is missing, stale, or incomplete,
+> create or update it with `references/studio-docs/templates/game-pillars.md` as
+> the structure. The initial brainstorm version must capture core fantasy, unique
+> hook, target MDA aesthetics, 3-5 pillars, design tests, anti-pillars, conflict
+> priority, and validation status; deeper cross-department implications can be
+> marked TBD for later refinement. Begin the response with the required verdict
+> token, then state whether the pillar document is current, created, updated, or
+> blocked."
 
 **Verdicts**: APPROVE / CONCERNS / REJECT