Unity Project Planner
Plan and architect Unity game projects with 6 specialized agents, 5 document types, and full MCP Unity tool integration. Inspired by the BMad Method, adapted for game development.
Prerequisites
- Unity project open with MCP Unity connected
- MCP Unity skill installed at
~/.claude/skills/mcp-unity/
Slash Commands
| Command |
Agent |
Produces |
Phase |
/unity-plan |
Producer |
Status YAML + routes to other commands |
Orchestrator |
/gdd |
Game Designer |
Game Design Document |
Analysis |
/tdd-unity |
Technical Director |
Technical Design Document |
Solutioning |
/level-design |
Level Designer |
Level Design Document |
Solutioning |
/art-direction |
Art Director |
Art Bible / Style Guide |
Solutioning |
/milestone |
Producer |
Milestone Plan |
Planning |
/unity-story |
Unity Developer |
Implementation stories with MCP sequences |
Implementation |
/unity-review |
Technical Director |
Architecture audit report |
Review |
Project Level System
The skill adapts document depth based on project scale:
| Level |
Name |
Timeline |
Documents |
Milestones |
| 0 |
Prototype |
1-3 days |
GDD mini + TDD mini |
Prototype only |
| 1 |
Game Jam |
2-7 days |
GDD compact + TDD compact |
Proto + Submission |
| 2 |
Indie |
3-18 months |
All 5 documents |
Proto → VS → Alpha → Beta → Gold |
| 3 |
AA |
1-3 years |
All detailed |
Full + platform cert |
| 4 |
AAA |
2-5 years |
All exhaustive |
Full + post-launch |
Auto-detection via MCP Unity: scene count, asset count, package count, script count.
See project-levels.md for detection heuristics.
Quick Start: /unity-plan
- Detect project state via MCP Unity (
unity_get_editor_state, unity_get_project_overview)
- Determine project level (auto-detect or ask user) — see helpers.md#H2
- Create status YAML at
.claude/context/unity-planner/unity-planner-status.yaml
- Ask user which documents to generate first
- Route to the appropriate command (
/gdd, /tdd-unity, etc.)
- Save status after each document generation
Agents
6 specialized agents, each with defined MCP Unity tool access:
| Agent |
Role |
Key MCP Tools |
| Game Designer |
GDD, mechanics, systems, core loop |
unity_get_project_overview (read-only) |
| Technical Director |
Architecture, ECS vs MonoBehaviour, pipeline |
unity_get_render_pipeline_info, unity_get_build_settings, unity_list_packages, unity_get_script_info |
| Level Designer |
Scenes, terrain, lighting, navigation |
unity_get_scene_info, unity_list_gameobjects, unity_get_terrain_info, unity_get_lightmap_settings |
| Producer |
Milestones, scope, risks, orchestration |
unity_get_project_overview, unity_get_build_settings |
| Unity Developer |
Implementation via all 164 MCP tools |
ALL tools — cross-ref ~/.claude/skills/mcp-unity/SKILL.md |
| Art Director |
Visual style, materials, UI, post-processing |
unity_get_render_pipeline_info, unity_get_material, unity_search_assets |
Full agent definitions: agents.md
Document Outputs
| Document |
Command |
Template |
Save Location |
| Game Design Document |
/gdd |
gdd-template.md |
.claude/context/unity-planner/gdd-{project}.md |
| Technical Design Doc |
/tdd-unity |
tdd-unity-template.md |
.claude/context/unity-planner/tdd-{project}.md |
| Level Design Doc |
/level-design |
level-design-template.md |
.claude/context/unity-planner/level-{name}.md |
| Art Bible |
/art-direction |
art-bible-template.md |
.claude/context/unity-planner/art-{project}.md |
| Milestone Plan |
/milestone |
milestone-template.md |
.claude/context/unity-planner/milestones-{project}.md |
Integration with MCP Unity
4 layers of integration:
- Read-only inspection (planning phase): All agents use MCP Unity read tools to understand the project before generating documents. No modifications during planning.
- Tool workflow recipes (implementation):
/unity-story produces step-by-step MCP tool sequences. See mcp-unity-workflows.md.
- Cross-skill reference: Points to
~/.claude/skills/mcp-unity/SKILL.md for tool details. Never duplicates the 164-tool reference.
- Tool category activation: Each workflow specifies which categories to enable via
unity_enable_tool_category. See helpers.md#H12.
Status Tracking
YAML status persists between sessions at .claude/context/unity-planner/unity-planner-status.yaml.
Tracks: project metadata, document status (none/draft/review/approved), milestone progress (planned/in_progress/completed), feature pillars (P0-P3), architecture decisions.
Schema: status-tracking.md
Helper Pattern
Detailed procedures are in helpers.md as numbered sections (H1-H12). Commands reference helpers.md#HN instead of embedding full instructions. This achieves ~70-85% token savings following the BMad pattern.
| Helper |
Purpose |
| H1 |
Project State Detection |
| H2 |
Project Level Detection |
| H3 |
Orchestrator Workflow |
| H4 |
GDD Generation |
| H5 |
Technical Design |
| H6 |
Level Design |
| H7 |
Art Direction |
| H8 |
Milestone Planning |
| H9 |
Unity Story Creation |
| H10 |
Architecture Review |
| H11 |
Document Save Convention |
| H12 |
MCP Tool Category Activation |
Rules
- Never modify Unity project files during planning — planning is read-only
- Always use MCP Unity tools for project inspection (never guess project state)
- Save all outputs to
.claude/context/unity-planner/
- Detect project level before generating any document
- Adapt document depth to project level (sections tagged
[LEVEL+])
- Cross-reference MCP Unity skill for tool details — never duplicate
- Update status YAML after every command execution
Related Skills
~/.claude/skills/mcp-unity/ — MCP Unity tool reference (164 tools)/brainstorm — Explore game ideas before /gdd/decompose — Break down features into tasks before /unity-story/start — Create feature branch after planning/team — Orchestrate parallel agent work on implementation
1---2name: unity-planner3description: Unity Project Planner4---5# Unity Project Planner67Plan and architect Unity game projects with 6 specialized agents, 5 document types, and full MCP Unity tool integration. Inspired by the BMad Method, adapted for game development.89## Prerequisites1011- Unity project open with MCP Unity connected12- MCP Unity skill installed at `~/.claude/skills/mcp-unity/`1314## Slash Commands1516| Command | Agent | Produces | Phase |17|---------|-------|----------|-------|18| `/unity-plan` | Producer | Status YAML + routes to other commands | Orchestrator |19| `/gdd` | Game Designer | Game Design Document | Analysis |20| `/tdd-unity` | Technical Director | Technical Design Document | Solutioning |21| `/level-design` | Level Designer | Level Design Document | Solutioning |22| `/art-direction` | Art Director | Art Bible / Style Guide | Solutioning |23| `/milestone` | Producer | Milestone Plan | Planning |24| `/unity-story` | Unity Developer | Implementation stories with MCP sequences | Implementation |25| `/unity-review` | Technical Director | Architecture audit report | Review |2627## Project Level System2829The skill adapts document depth based on project scale:3031| Level | Name | Timeline | Documents | Milestones |32|-------|------|----------|-----------|------------|33| 0 | Prototype | 1-3 days | GDD mini + TDD mini | Prototype only |34| 1 | Game Jam | 2-7 days | GDD compact + TDD compact | Proto + Submission |35| 2 | Indie | 3-18 months | All 5 documents | Proto → VS → Alpha → Beta → Gold |36| 3 | AA | 1-3 years | All detailed | Full + platform cert |37| 4 | AAA | 2-5 years | All exhaustive | Full + post-launch |3839Auto-detection via MCP Unity: scene count, asset count, package count, script count.40See [project-levels.md](references/workflows/project-levels.md) for detection heuristics.4142## Quick Start: `/unity-plan`43441. **Detect project state** via MCP Unity (`unity_get_editor_state`, `unity_get_project_overview`)452. **Determine project level** (auto-detect or ask user) — see [helpers.md#H2](references/helpers.md)463. **Create status YAML** at `.claude/context/unity-planner/unity-planner-status.yaml`474. **Ask user** which documents to generate first485. **Route** to the appropriate command (`/gdd`, `/tdd-unity`, etc.)496. **Save status** after each document generation5051## Agents52536 specialized agents, each with defined MCP Unity tool access:5455| Agent | Role | Key MCP Tools |56|-------|------|---------------|57| **Game Designer** | GDD, mechanics, systems, core loop | `unity_get_project_overview` (read-only) |58| **Technical Director** | Architecture, ECS vs MonoBehaviour, pipeline | `unity_get_render_pipeline_info`, `unity_get_build_settings`, `unity_list_packages`, `unity_get_script_info` |59| **Level Designer** | Scenes, terrain, lighting, navigation | `unity_get_scene_info`, `unity_list_gameobjects`, `unity_get_terrain_info`, `unity_get_lightmap_settings` |60| **Producer** | Milestones, scope, risks, orchestration | `unity_get_project_overview`, `unity_get_build_settings` |61| **Unity Developer** | Implementation via all 164 MCP tools | ALL tools — cross-ref `~/.claude/skills/mcp-unity/SKILL.md` |62| **Art Director** | Visual style, materials, UI, post-processing | `unity_get_render_pipeline_info`, `unity_get_material`, `unity_search_assets` |6364Full agent definitions: [agents.md](references/agents.md)6566## Document Outputs6768| Document | Command | Template | Save Location |69|----------|---------|----------|---------------|70| Game Design Document | `/gdd` | [gdd-template.md](references/templates/gdd-template.md) | `.claude/context/unity-planner/gdd-{project}.md` |71| Technical Design Doc | `/tdd-unity` | [tdd-unity-template.md](references/templates/tdd-unity-template.md) | `.claude/context/unity-planner/tdd-{project}.md` |72| Level Design Doc | `/level-design` | [level-design-template.md](references/templates/level-design-template.md) | `.claude/context/unity-planner/level-{name}.md` |73| Art Bible | `/art-direction` | [art-bible-template.md](references/templates/art-bible-template.md) | `.claude/context/unity-planner/art-{project}.md` |74| Milestone Plan | `/milestone` | [milestone-template.md](references/templates/milestone-template.md) | `.claude/context/unity-planner/milestones-{project}.md` |7576## Integration with MCP Unity77784 layers of integration:79801. **Read-only inspection** (planning phase): All agents use MCP Unity read tools to understand the project before generating documents. No modifications during planning.812. **Tool workflow recipes** (implementation): `/unity-story` produces step-by-step MCP tool sequences. See [mcp-unity-workflows.md](references/workflows/mcp-unity-workflows.md).823. **Cross-skill reference**: Points to `~/.claude/skills/mcp-unity/SKILL.md` for tool details. Never duplicates the 164-tool reference.834. **Tool category activation**: Each workflow specifies which categories to enable via `unity_enable_tool_category`. See [helpers.md#H12](references/helpers.md).8485## Status Tracking8687YAML status persists between sessions at `.claude/context/unity-planner/unity-planner-status.yaml`.8889Tracks: project metadata, document status (none/draft/review/approved), milestone progress (planned/in_progress/completed), feature pillars (P0-P3), architecture decisions.9091Schema: [status-tracking.md](references/schema/status-tracking.md)9293## Helper Pattern9495Detailed procedures are in [helpers.md](references/helpers.md) as numbered sections (H1-H12). Commands reference `helpers.md#HN` instead of embedding full instructions. This achieves ~70-85% token savings following the BMad pattern.9697| Helper | Purpose |98|--------|---------|99| H1 | Project State Detection |100| H2 | Project Level Detection |101| H3 | Orchestrator Workflow |102| H4 | GDD Generation |103| H5 | Technical Design |104| H6 | Level Design |105| H7 | Art Direction |106| H8 | Milestone Planning |107| H9 | Unity Story Creation |108| H10 | Architecture Review |109| H11 | Document Save Convention |110| H12 | MCP Tool Category Activation |111112## Rules113114- **Never modify Unity project files during planning** — planning is read-only115- **Always use MCP Unity tools** for project inspection (never guess project state)116- **Save all outputs** to `.claude/context/unity-planner/`117- **Detect project level** before generating any document118- **Adapt document depth** to project level (sections tagged `[LEVEL+]`)119- **Cross-reference MCP Unity skill** for tool details — never duplicate120- **Update status YAML** after every command execution121122## Related Skills123124- `~/.claude/skills/mcp-unity/` — MCP Unity tool reference (164 tools)125- `/brainstorm` — Explore game ideas before `/gdd`126- `/decompose` — Break down features into tasks before `/unity-story`127- `/start` — Create feature branch after planning128- `/team` — Orchestrate parallel agent work on implementation
JulianKerignard