diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json index 8c564d3..d0e6407 100644 --- a/.codex-plugin/plugin.json +++ b/.codex-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "codex-game-studios", - "version": "0.1.0", + "version": "0.1.1", "description": "A Codex plugin for building game-production workflows step by step, starting with guided game concept brainstorming.", "author": { "name": "wxm", diff --git a/agents/art-director.toml b/.codex/agents/art-director.toml similarity index 100% rename from agents/art-director.toml rename to .codex/agents/art-director.toml diff --git a/agents/creative-director.toml b/.codex/agents/creative-director.toml similarity index 100% rename from agents/creative-director.toml rename to .codex/agents/creative-director.toml diff --git a/agents/producer.toml b/.codex/agents/producer.toml similarity index 100% rename from agents/producer.toml rename to .codex/agents/producer.toml diff --git a/agents/technical-director.toml b/.codex/agents/technical-director.toml similarity index 100% rename from agents/technical-director.toml rename to .codex/agents/technical-director.toml diff --git a/README.md b/README.md index cb84ed3..bad9e6e 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ This repository is the minimal starting framework for a Codex plugin. Current state: - Skills: `/brainstorm` -- Agents: `creative-director`, `art-director`, `technical-director`, `producer` +- Codex custom agents: `creative-director`, `art-director`, `technical-director`, `producer` - Assets: `codex-game-studio.svg` - References: `director-gates.md`, `templates/game-concept.md` - Standards: `design-docs.md` @@ -16,6 +16,15 @@ Current state: - No MCP servers - No app integrations +The director agents are pre-defined Codex custom agents stored in: + +```text +.codex/agents/ +``` + +Each custom agent is a standalone TOML file with `name`, `description`, and +`developer_instructions`, matching the Codex subagents documentation. + The only required plugin manifest is: ```text diff --git a/commands/brainstorm.md b/commands/brainstorm.md index bfad852..56a6d15 100644 --- a/commands/brainstorm.md +++ b/commands/brainstorm.md @@ -11,5 +11,5 @@ Pass any text after `/brainstorm` as workflow input. 1. Use `../skills/brainstorm/SKILL.md` as the workflow entry point. 2. Read `../skills/brainstorm/DETAILS.md` when present for the full procedure. 3. Apply project guidance from `AGENTS.md` and relevant files in `../standards/` before changing project files. -4. Use `../agents/.toml` when the skill delegates to a custom agent. +4. Use the pre-defined Codex custom agents in `../.codex/agents/.toml` when the skill delegates to a subagent. 5. Return decisions, changes, blockers, verification, and next steps. diff --git a/references/studio-docs/director-gates.md b/references/studio-docs/director-gates.md index d432a89..0a92239 100644 --- a/references/studio-docs/director-gates.md +++ b/references/studio-docs/director-gates.md @@ -4,8 +4,9 @@ This document defines the standard gate prompts for all director and lead review across every workflow stage. Skills reference gate IDs from this document instead of embedding full prompts inline — eliminating drift when prompts need updating. -**Scope**: All 7 production stages (Concept → Release), all 3 Tier 1 directors, -all key Tier 2 leads. Any skill, team orchestrator, or workflow may invoke these gates. +**Scope**: All 7 production stages (Concept → Release), all shared director +custom agents, and all key Tier 2 leads. Any skill, team orchestrator, or +workflow may invoke these gates. --- @@ -14,12 +15,17 @@ 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 subagent delegation using gate **CD-PILLARS** from -`docs/game-studio/director-gates.md`. +Spawn `creative-director` via Codex custom-agent delegation using gate +**CD-PILLARS** from `references/studio-docs/director-gates.md`. ``` -Pass the context listed under that gate's **Context to pass** field, then handle -the verdict using the **Verdict handling** rules below. +The matching custom agent must already be defined at +`.codex/agents/.toml`. Pass the context listed under that gate's +**Context to pass** field, then handle the verdict using the **Verdict +handling** rules below. + +Director names are Codex custom agent names. Do not recreate them by pasting +profile text into a generic default agent. --- @@ -78,9 +84,11 @@ Apply the resolved mode: ``` # Apply mode check, then: -Spawn `[agent-name]` via subagent delegation: -- Gate: [GATE-ID] (see docs/game-studio/director-gates.md) +Spawn `[agent-name]` via Codex custom-agent delegation: +- Gate: [GATE-ID] (see references/studio-docs/director-gates.md) +- Custom agent file: .codex/agents/[agent-name].toml - Context: [fields listed under that gate] +- Codex fork_context: false unless full thread context is required - Await the verdict before proceeding. ``` @@ -88,8 +96,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 subagent delegation — issue all subagent requests before -waiting for any result. Collect all verdicts before proceeding. +Spawn all [N] custom agents simultaneously via Codex subagent delegation. Issue +all subagent requests before waiting for any result. Collect all verdicts before +proceeding. ``` --- @@ -124,7 +133,7 @@ For phase gates, record in `docs/architecture/architecture.md` or ## Tier 1 — Creative Director Gates -Agent: `creative-director` | Model tier: Opus | Domain: Vision, pillars, player experience +Agent: `creative-director` | Custom agent file: `.codex/agents/creative-director.toml` | Domain: Vision, pillars, player experience --- @@ -266,7 +275,7 @@ any session that produces player feedback ## Tier 1 — Technical Director Gates -Agent: `technical-director` | Model tier: Opus | Domain: Architecture, engine risk, performance +Agent: `technical-director` | Custom agent file: `.codex/agents/technical-director.toml` | Domain: Architecture, engine risk, performance --- @@ -412,7 +421,7 @@ or before finalizing any engine-specific implementation approach ## Tier 1 — Producer Gates -Agent: `producer` | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk +Agent: `producer` | Custom agent file: `.codex/agents/producer.toml` | Domain: Scope, timeline, dependencies, production risk --- @@ -538,7 +547,7 @@ is invoked ## Tier 1 — Art Director Gates -Agent: `art-director` | Model tier: Sonnet | Domain: Visual identity, art bible, visual production readiness +Agent: `art-director` | Custom agent file: `.codex/agents/art-director.toml` | Domain: Visual identity, art bible, visual production readiness --- @@ -573,7 +582,7 @@ Agent: `art-director` | Model tier: Sonnet | Domain: Visual identity, art bible, **Context to pass**: - Art bible path (`design/art/art-bible.md`) - Game pillars and core fantasy -- Platform and performance constraints (from `docs/game-studio/technical-preferences.md` if configured) +- Platform and performance constraints (from the project technical preferences document, if configured) - Visual identity anchor chosen during brainstorm (from `design/gdd/game-concept.md`) **Prompt**: @@ -619,7 +628,9 @@ Agent: `art-director` | Model tier: Sonnet | Domain: Visual identity, art bible, ## Tier 2 — Lead Gates These gates are invoked by orchestration skills and senior skills when a domain -specialist's feasibility sign-off is needed. Tier 2 leads use Sonnet (default). +specialist's feasibility sign-off is needed. If a Tier 2 lead custom agent is +added later, invoke it with the same Codex custom-agent delegation pattern used +for Tier 1 agents. --- diff --git a/skills/brainstorm/DETAILS.md b/skills/brainstorm/DETAILS.md index 73a1f68..fe1aac6 100644 --- a/skills/brainstorm/DETAILS.md +++ b/skills/brainstorm/DETAILS.md @@ -11,6 +11,10 @@ When this skill is invoked: See `../../references/studio-docs/director-gates.md` for the full check pattern. + When a gate is active, spawn the named Codex custom agent that is already + defined in `../../.codex/agents/.toml`. Do not recreate the + director role by pasting profile text into a generic default agent. + 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) @@ -195,7 +199,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 subagent delegation in parallel before moving to Phase 5. Issue both subagent 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` 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. @@ -253,7 +257,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 subagent delegation using gate TD-FEASIBILITY (`../../references/studio-docs/director-gates.md`) before scope tiers are defined.** +**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.** Pass: core loop description, platform target, engine choice (or "undecided"), list of identified technical risks. @@ -264,7 +268,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 subagent delegation using gate PR-SCOPE (`../../references/studio-docs/director-gates.md`).** +**After scope tiers are defined, spawn `producer` via Codex custom-agent delegation using gate PR-SCOPE (`../../references/studio-docs/director-gates.md`).** Pass: full vision scope, MVP definition, timeline estimate, team size. @@ -307,7 +311,7 @@ If yes, generate the document using the template at `../../references/studio-doc 1. "Run `/setup-engine` to configure the engine and populate version-aware reference docs" 2. "Run `/art-bible` to create the visual identity specification — do this BEFORE writing GDDs. **The art bible is required before the Technical Setup gate.** It gates asset production and shapes technical architecture decisions (rendering, VFX, UI systems)." 3. "Use `/design-review design/gdd/game-concept.md` to validate concept completeness before going downstream" - 4. "Discuss vision with the `creative-director` agent for pillar refinement" + 4. "Discuss vision with the `creative-director` custom agent for pillar refinement" 5. "Decompose the concept into individual systems with `/map-systems` — maps dependencies, assigns priorities, and creates the systems index" 6. "Author per-system GDDs with `/design-system` — guided, section-by-section GDD writing for each system identified in step 5" 7. "Plan the technical architecture with `/create-architecture` — produces the master architecture blueprint and Required ADR list" diff --git a/skills/brainstorm/SKILL.md b/skills/brainstorm/SKILL.md index 66ec4da..031c905 100644 --- a/skills/brainstorm/SKILL.md +++ b/skills/brainstorm/SKILL.md @@ -7,4 +7,4 @@ description: "Use when you need the /brainstorm game-production workflow. Guided Run the `/brainstorm` Codex Game Studio workflow. -Before acting, read `DETAILS.md` for the full workflow. Apply project guidance from `AGENTS.md`, use `../../standards/` for path-specific standards, and use `../../agents/.toml` when the workflow delegates to a custom agent. +Before acting, read `DETAILS.md` for the full workflow. Apply project guidance from `AGENTS.md`, use `../../standards/` for path-specific standards, and use the pre-defined Codex custom agents in `../../.codex/agents/.toml` when the workflow delegates to a subagent.