迁移setup-engine工作流

project-template/AGENTS.md

@@ -12,8 +12,19 @@ game-production workflows.
 - **Build System**: [SPECIFY after choosing engine]
 - **Asset Pipeline**: [SPECIFY after choosing engine]
 
-> Engine-specialist agents will be added later. For now, use the four bundled
-> director agents only when a workflow explicitly asks for them.
+Run `$setup-engine` after `$brainstorm` or whenever the project needs its engine,
+version, language, and specialist routing initialized.
+
+## Engine Version Reference
+
+Pinned engine/version reference is created by `$setup-engine`:
+
+```text
+docs/engine-reference/<engine>/VERSION.md
+```
+
+When the file exists, read it before giving engine-specific implementation
+guidance.
 
 ## Runtime Agents
 
@@ -23,15 +34,26 @@ Bundled custom agents are installed into:
 .codex/agents/
 ```
 
-Current bundled agents:
+Bundled director agents:
 
 - `creative-director`
 - `art-director`
 - `technical-director`
 - `producer`
 
-These agents are primarily used by director / lead review gates. They are not a
-replacement for user decisions.
+Bundled engine specialist agents:
+
+- Godot: `godot-specialist`, `godot-gdscript-specialist`,
+  `godot-csharp-specialist`, `godot-shader-specialist`,
+  `godot-gdextension-specialist`
+- Unity: `unity-specialist`, `unity-dots-specialist`,
+  `unity-shader-specialist`, `unity-addressables-specialist`,
+  `unity-ui-specialist`
+- Unreal: `unreal-specialist`, `ue-blueprint-specialist`,
+  `ue-gas-specialist`, `ue-replication-specialist`, `ue-umg-specialist`
+
+Director agents are used by review gates. Engine specialists are routed through
+`docs/technical-preferences.md`. They are not replacements for user decisions.
 
 ## Review Intensity
 
@@ -44,7 +66,7 @@ production/review-mode.txt
 Allowed values:
 
 - `full` — all gates active; every workflow step is reviewed.
-- `lean` — PHASE-GATEs only (`/gate-check`); per-skill gates are skipped.
+- `lean` — phase-level gates only; ordinary per-skill gates are skipped.
 - `solo` — no director gates anywhere.
 
 Default when the file is missing: `lean`.
@@ -67,44 +89,42 @@ Question -> Options -> Decision -> Draft -> Approval
 
 ## Current Workflow Surface
 
-The current plugin build exposes only the migrated `/brainstorm` workflow.
+The current plugin build exposes these workflows:
 
-`/brainstorm` produces:
+- `$brainstorm` guides concept ideation and produces:
 
 ```text
 design/gdd/game-concept.md
 ```
 
-Game pillars and anti-pillars are defined during `/brainstorm` and recorded
+Game pillars and anti-pillars are defined during `$brainstorm` and recorded
 inside `design/gdd/game-concept.md`. A separate `design/gdd/game-pillars.md`
 may be created later from the template if the project needs a standalone
 pillar source of truth.
 
-## Design Documents
-
-Use these project paths:
+- `$setup-engine` configures the project technology stack and produces or
+  updates:
 
 ```text
-design/gdd/
-design/ux/
-docs/architecture/
-production/
+AGENTS.md
+docs/technical-preferences.md
+docs/engine-reference/<engine>/VERSION.md
 ```
 
-`design/gdd/game-concept.md`, optional `design/gdd/game-pillars.md`, and
-`design/gdd/systems-index.md` are top-level design documents. They are not
-per-system GDDs.
+## Project Documents
 
-Per-system GDDs under `design/gdd/` should include:
+Current workflows use these project paths:
 
-1. Overview
-2. Player Fantasy
-3. Detailed Rules
-4. Formulas
-5. Edge Cases
-6. Dependencies
-7. Tuning Knobs
-8. Acceptance Criteria
+```text
+design/gdd/game-concept.md
+docs/technical-preferences.md
+docs/engine-reference/<engine>/VERSION.md
+production/review-mode.txt
+```
+
+`docs/technical-preferences.md` records engine/language conventions, platform
+targets, performance budgets, approved libraries, and engine specialist routing.
+Do not assume workflows beyond the current plugin surface are available.
 
 ## Context Management