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

skills/brainstorm/DETAILS.md

@@ -11,6 +11,12 @@ When this skill is invoked:
 
    See `../../references/studio-docs/director-gates.md` for the full check pattern.
 
+   Review mode controls **director / lead review gates only**. It is not a
+   blanket rule for all custom-agent or subagent usage. For `/brainstorm`, the
+   current agent calls are review gates, so `lean` skips CD-PILLARS,
+   AD-CONCEPT-VISUAL, TD-FEASIBILITY, and PR-SCOPE; `full` runs them; `solo`
+   skips all director review gates.
+
    Director agent source files live in `../../runtime/agents/`. Before running
    any `full` review-mode gate, verify the target project has the matching
    `.codex/agents/<agent-name>.toml` files installed. If they are missing, run
@@ -203,15 +209,36 @@ If the user selects B, C, or D, make the revision, then use a structured prompt
 
 Repeat until the user selects [A] Lock these in.
 
+Treat `[A] Lock these in` as approval to create or update
+`design/gdd/game-pillars.md` during this `/brainstorm` run. The file is a
+brainstorm-stage artifact: start it lightweight now, then let later workflows
+deepen it as the project matures.
+
+**Pillar conflict priority**: After pillars are locked, ask one short follow-up:
+"If two pillars conflict, which one wins first?" Present the locked pillar names
+as ordered options and let the user rank them or describe a custom priority.
+Record this as the initial conflict-resolution order in
+`design/gdd/game-pillars.md`.
+
 **Review mode check** — apply before spawning CD-PILLARS and AD-CONCEPT-VISUAL:
-- `solo` → skip both. Note: "CD-PILLARS skipped — Solo mode. AD-CONCEPT-VISUAL skipped — Solo mode." Proceed to Phase 5.
-- `lean` → skip both (not PHASE-GATEs). Note: "CD-PILLARS skipped — Lean mode. AD-CONCEPT-VISUAL skipped — Lean mode." Proceed to Phase 5.
+- `solo` → skip both. Note: "CD-PILLARS skipped — Solo mode. AD-CONCEPT-VISUAL skipped — Solo mode." Create or update the initial `design/gdd/game-pillars.md` directly from the locked pillars, then proceed to Phase 5.
+- `lean` → skip both (not PHASE-GATEs). Note: "CD-PILLARS skipped — Lean mode. AD-CONCEPT-VISUAL skipped — Lean mode." Create or update the initial `design/gdd/game-pillars.md` directly from the locked pillars, then proceed to Phase 5.
 - `full` → spawn as normal.
 
 **After pillars and anti-pillars are agreed, spawn BOTH `creative-director` AND `art-director` via Codex custom-agent delegation in parallel before moving to Phase 5. Issue both subagent requests simultaneously — do not wait for one before starting the other.**
 
 - **`creative-director`** — gate **CD-PILLARS** (`../../references/studio-docs/director-gates.md`)
-  Pass: full pillar set with design tests, anti-pillars, core fantasy, unique hook.
+  Pass: full pillar set with design tests, anti-pillars, pillar conflict priority,
+  core fantasy, unique hook.
+  Also pass whether `design/gdd/game-pillars.md` already exists and whether its
+  contents match the locked pillar set. This file is required for `/brainstorm`:
+  if it already exists and still matches the locked pillars, the subagent reviews
+  it in place and avoids rewriting for churn; if the file is missing, stale, or
+  incomplete, the subagent creates or updates it from
+  `../../references/studio-docs/templates/game-pillars.md`. The initial version
+  only needs the brainstorm-level material: core fantasy, unique hook, target
+  MDA aesthetics, 3-5 pillars, design tests, anti-pillars, conflict priority,
+  and a validation checklist.
 
 - **`art-director`** — gate **AD-CONCEPT-VISUAL** (`../../references/studio-docs/director-gates.md`)
   Pass: game concept elevator pitch, full pillar set with design tests, target platform (if known), any reference games or visual touchstones the user mentioned.
@@ -285,10 +312,20 @@ Present the assessment to the user. If UNREALISTIC, offer to adjust the MVP defi
 
 ---
 
-4. **Generate the game concept document** using the template at
-   `../../references/studio-docs/templates/game-concept.md`. Fill in ALL sections from the
-   brainstorm conversation, including the MDA analysis, player motivation
-   profile, and flow state design sections.
+4. **Generate the brainstorm documents**:
+
+   - Generate or update `design/gdd/game-pillars.md` using
+     `../../references/studio-docs/templates/game-pillars.md`. This file is
+     created during `/brainstorm`, even if it starts lightweight. If review mode
+     is `full`, the `creative-director` subagent owns this write during
+     CD-PILLARS. If review mode is `lean` or `solo`, the main brainstorm workflow
+     writes the initial version directly after pillars are locked.
+   - Generate `design/gdd/game-concept.md` using
+     `../../references/studio-docs/templates/game-concept.md`. Fill in ALL
+     sections from the brainstorm conversation, including the MDA analysis,
+     player motivation profile, and flow state design sections.
+   - In `design/gdd/game-concept.md`, summarize the locked pillars and link to
+     `design/gdd/game-pillars.md` as the detailed pillar source of truth.
 
    **Include a Visual Identity Anchor section** in the game concept document with:
    - The selected visual direction name
@@ -300,16 +337,20 @@ Present the assessment to the user. If UNREALISTIC, offer to adjust the MVP defi
    move" decision before it can be forgotten between sessions.
 
 5. Use a structured prompt or direct chat question for write approval:
-- Prompt: "Game concept is ready. May I write it to `design/gdd/game-concept.md`?"
-- Options: `[A] Yes — write it` / `[B] Not yet — revise a section first`
+- Prompt: "Brainstorm documents are ready. May I write them to `design/gdd/game-concept.md` and `design/gdd/game-pillars.md`?"
+- Options: `[A] Yes — write them` / `[B] Not yet — revise a section first`
 
 If [B]: ask which section to revise using a structured prompt with options: `Elevator Pitch` / `Core Fantasy & Unique Hook` / `Pillars` / `Core Loop` / `MVP Definition` / `Scope Tiers` / `Risks` / `Something else — I'll describe`
 
-After revising, show the updated section as a diff or clear before/after, then ask — "Ready to write the updated concept document?"
-Options: `[A] Yes — write it` / `[B] Revise another section`
+After revising, show the updated section as a diff or clear before/after, then ask — "Ready to write the updated brainstorm documents?"
+Options: `[A] Yes — write them` / `[B] Revise another section`
 Repeat until the user selects [A].
 
-If yes, generate the document using the template at `../../references/studio-docs/templates/game-concept.md`, fill in ALL sections from the brainstorm conversation, and write the file, creating directories as needed.
+If yes, generate `design/gdd/game-pillars.md` using
+`../../references/studio-docs/templates/game-pillars.md` and
+`design/gdd/game-concept.md` using
+`../../references/studio-docs/templates/game-concept.md`, fill both from the
+brainstorm conversation, and write the files, creating directories as needed.
 
 **Scope consistency rule**: The "Estimated Scope" field in the Core Identity table must match the full-vision timeline from the Scope Tiers section — not just say "Large (9+ months)". Write it as "Large (X–Y months, solo)" or "Large (X–Y months, team of N)" so the summary table is accurate.
 
@@ -336,7 +377,7 @@ If yes, generate the document using the template at `../../references/studio-doc
    5. "After full design and architecture, build the `/vertical-slice` to validate production readiness before committing to sprints"
 
 7. **Output a summary** with the chosen concept's elevator pitch, pillars,
-   primary player type, engine recommendation, biggest risk, and file path.
+   primary player type, engine recommendation, biggest risk, and file paths.
 
 Verdict: **COMPLETE** — game concept created and handed off for next steps.
 

skills/brainstorm/SKILL.md

@@ -10,3 +10,14 @@ Run the Codex Game Studios brainstorm workflow.
 Before acting, read `DETAILS.md` for the full workflow. Apply project guidance from `AGENTS.md` and use `../../standards/` for path-specific standards.
 
 Director gates use the bundled custom agents from `../../runtime/agents/`. If the current project does not already have those agents installed in `.codex/agents/`, run `$setup-runtime` first.
+
+Review mode controls review-gate intensity, not all custom-agent usage:
+`full` runs key director/lead gates, `lean` runs only PHASE-GATE checks such as
+`/gate-check`, and `solo` skips director review gates.
+
+`/brainstorm` writes two brainstorm-stage artifacts:
+`design/gdd/game-concept.md` and `design/gdd/game-pillars.md`. In
+`--review full` mode, `/brainstorm` calls the `creative-director` custom agent
+during the CD-PILLARS gate and gives that subagent responsibility for creating
+or updating `design/gdd/game-pillars.md`. In `lean` or `solo` mode, the main
+brainstorm workflow writes the initial pillar document directly.

skills/using-codex-game-studios/SKILL.md

@@ -14,6 +14,16 @@ Codex Game Studios is a game-production plugin built around plugin-discovered sk
 - Use `runtime/agents/` as the plugin source of bundled custom agents.
 - Use `references/` and `standards/` only when the active workflow points to them.
 
+## Review Intensity
+
+`production/review-mode.txt` controls review-gate intensity, not whether agents
+exist or whether future team workflows may use subagents for core work:
+
+- `full` — all key director / lead review gates call their custom agents.
+- `lean` — only PHASE-GATE review gates such as `/gate-check` call directors;
+  ordinary per-skill review gates are skipped.
+- `solo` — all director review gates are skipped.
+
 ## Design Rule
 
 Do not rely on a global `~/.codex/skills/codex-game-studio` bridge. The installed plugin exposes its skills through `.codex-plugin/plugin.json` with `"skills": "./skills/"`, matching the normal Codex plugin layout.