明确brainstorm使用Codex子代理工作流

README.md

@@ -10,7 +10,7 @@ skills expose the runtime workflows directly. Do not use a global
 - Skills:
   - `$brainstorm` guides game concept ideation into `design/gdd/game-concept.md`.
   - `$setup-engine` configures engine/version, technical preferences, engine reference docs, and specialist routing.
-- Runtime agents:
+- Runtime agents for Codex subagent workflows:
   - Director agents: `creative-director`, `art-director`, `technical-director`, `producer`
   - Godot specialists: `godot-specialist`, `godot-gdscript-specialist`, `godot-csharp-specialist`, `godot-shader-specialist`, `godot-gdextension-specialist`
   - Unity specialists: `unity-specialist`, `unity-dots-specialist`, `unity-shader-specialist`, `unity-addressables-specialist`, `unity-ui-specialist`
@@ -36,8 +36,8 @@ engine version, writes the Technology Stack section in `AGENTS.md`, creates
 
 ## Runtime Setup
 
-To install the bundled custom agents into a game project, run the installer
-directly:
+To install the bundled project-scoped custom agents into a game project, run
+the installer directly:
 
 ```bash
 python3 scripts/install_codex_runtime.py /path/to/game-project
@@ -52,7 +52,8 @@ project guide to:
 ```
 
 Each runtime agent is a standalone TOML file with `name`, `description`, and
-`developer_instructions`, matching Codex custom-agent conventions.
+`developer_instructions`, matching Codex custom-agent conventions and usable by
+Codex subagent workflows.
 
 If the target project already has a different `AGENTS.md`, the installer reports
 a conflict and leaves it unchanged. Use `--force-agents-md` only when you intend

references/studio-docs/director-gates.md

@@ -14,7 +14,8 @@ all key Tier 2 leads. Any skill, team orchestrator, or workflow may invoke these
 In any skill, replace an inline director prompt with a reference:
 
 ```
-Spawn `creative-director` via Codex custom-agent delegation using gate
+Spawn `creative-director` through a Codex subagent workflow using the
+project-scoped custom agent in `.codex/agents/creative-director.toml` and gate
 **CD-PILLARS** from `references/studio-docs/director-gates.md`.
 ```
 
@@ -78,7 +79,8 @@ Apply the resolved mode:
 
 ```
 # Apply mode check, then:
-Spawn `[agent-name]` via Codex custom-agent delegation:
+Spawn `[agent-name]` as a Codex subagent using the project-scoped custom agent
+in `.codex/agents/`:
 - Gate: [GATE-ID] (see references/studio-docs/director-gates.md)
 - Context: [fields listed under that gate]
 - Await the verdict before proceeding.
@@ -88,8 +90,9 @@ For parallel spawning (multiple directors at the same gate point):
 
 ```
 # Apply mode check for each gate first, then spawn all that survive:
-Spawn all [N] agents simultaneously via Codex custom-agent delegation — issue all custom-agent requests before
-waiting for any result. Collect all verdicts before proceeding.
+Spawn all [N] agents simultaneously as Codex subagents — issue all subagent
+spawn requests before waiting for any result. Collect all verdicts before
+proceeding.
 ```
 
 ---
@@ -766,7 +769,7 @@ When a workflow requires multiple directors at the same checkpoint (most common
 at `/gate-check`), spawn all agents simultaneously:
 
 ```
-Spawn in parallel (issue all custom-agent requests before waiting for any result):
+Spawn in parallel (issue all subagent spawn requests before waiting for any result):
 1. creative-director  → gate CD-PHASE-GATE
 2. technical-director → gate TD-PHASE-GATE
 3. producer           → gate PR-PHASE-GATE

skills/brainstorm/DETAILS.md

@@ -11,6 +11,11 @@ When this skill is invoked:
 
    See `../../references/studio-docs/director-gates.md` for the full check pattern.
 
+   In `full` review mode, `$brainstorm` uses Codex subagent workflows with
+   project-scoped custom agents installed under `.codex/agents/`. Ensure these
+   four director agents are installed before running a full review:
+   `creative-director`, `art-director`, `technical-director`, and `producer`.
+
 2. **Check for existing concept work**:
    - Read `design/gdd/game-concept.md` if it exists (resume, don't restart)
    - Read `design/gdd/game-pillars.md` if it exists (build on established pillars)
@@ -259,7 +264,7 @@ Repeat until the user selects [A] Lock these in.
 - `lean` → skip both (not PHASE-GATEs). Note: "CD-PILLARS skipped — Lean mode. AD-CONCEPT-VISUAL skipped — Lean mode." 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 custom-agent requests simultaneously — do not wait for one before starting the other.**
+**After pillars and anti-pillars are agreed, spawn BOTH `creative-director` AND `art-director` through a Codex subagent workflow using the project-scoped custom agents in `.codex/agents/`. Spawn them in parallel before moving to Phase 5. Issue both subagent spawn requests before waiting for either result.**
 
 - **`creative-director`** — gate **CD-PILLARS** (`../../references/studio-docs/director-gates.md`)
   Pass: full pillar set with design tests, anti-pillars, core fantasy, unique hook.
@@ -318,7 +323,7 @@ Ground the concept in reality:
 - `lean` → skip (not a PHASE-GATE). Note: "TD-FEASIBILITY skipped — Lean mode." Proceed directly to scope tier definition.
 - `full` → spawn as normal.
 
-**After identifying biggest technical risks, spawn `technical-director` via Codex custom-agent delegation using gate TD-FEASIBILITY (`../../references/studio-docs/director-gates.md`) before scope tiers are defined.**
+**After identifying biggest technical risks, spawn `technical-director` through a Codex subagent workflow using the project-scoped custom agent in `.codex/agents/` and gate TD-FEASIBILITY (`../../references/studio-docs/director-gates.md`) before scope tiers are defined.**
 
 Pass: core loop description, platform target, engine choice (or "undecided"), list of identified technical risks.
 
@@ -329,7 +334,7 @@ Present the assessment to the user. If HIGH RISK, offer to revisit scope before
 - `lean` → skip (not a PHASE-GATE). Note: "PR-SCOPE skipped — Lean mode." Proceed to document generation.
 - `full` → spawn as normal.
 
-**After scope tiers are defined, spawn `producer` via Codex custom-agent delegation using gate PR-SCOPE (`../../references/studio-docs/director-gates.md`).**
+**After scope tiers are defined, spawn `producer` through a Codex subagent workflow using the project-scoped custom agent in `.codex/agents/` and gate PR-SCOPE (`../../references/studio-docs/director-gates.md`).**
 
 Pass: full vision scope, MVP definition, timeline estimate, team size.
 

skills/brainstorm/SKILL.md

@@ -9,9 +9,12 @@ 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/` or does not have root `AGENTS.md`, run
+Director gates run through Codex subagent workflows using the bundled
+project-scoped custom agents from `../../runtime/agents/`. In `full` review
+mode, `$brainstorm` explicitly spawns Codex subagents for the director gates.
+If the current project does not already have `.codex/agents/creative-director.toml`,
+`.codex/agents/art-director.toml`, `.codex/agents/technical-director.toml`,
+`.codex/agents/producer.toml`, or root `AGENTS.md`, run
 `python3 scripts/install_codex_runtime.py <target-project>` from the plugin root
 first.