wxm/codex-game-studios
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
wxm
2026-05-19 02:17:53 -07:00
parent 9629f8b8ef
commit 7c71d5dfde
4 changed files with 27 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
skills/brainstorm/DETAILS.md
View File

@@ -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.