A planning workflow for turning a game feature or sprint goal into ordered tasks. Each task includes dependencies, size, acceptance criteria—conditions that define when it is done—and a relevant skill.

Use it to plan Unity features or sprints, check architecture and dependencies, and create an actionable implementation checklist.

It makes project work easier to estimate and track by showing what must happen first and how completion will be judged.

uw-cmd-plan — Command by devdavv

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/devdavv/unity-ai-workflow/uw-cmd-plan

Clone the repo

git clone --depth 1 https://github.com/devdavv/unity-ai-workflow

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 430 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00430
Opus 5	$0.00000	$0.00215
Sonnet 5	$0.00000	$0.00086
Haiku 4.5	$0.00000	$0.00043

Measured 2d ago against content hash 7a5d730a2851, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

uw-cmd-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/uw-cmd-plan.md · 48 lines

What it actually says

/uw-cmd-plan — Planning Workflow

Break a feature or sprint into actionable tasks with clear acceptance criteria.

Steps

1. Define the Feature

Ask the user:

What feature or sprint goal are we planning?
Which GDD scenario(s) does this map to?
Are there dependencies on existing systems?

2. Architecture Check

Read docs/TDD.md to understand:

Which assemblies are involved
Data flow between systems
Any API constraints

3. Task Breakdown

Create a numbered task list with:

Task name (action-oriented: "Implement X", "Create Y")
Estimated complexity (S/M/L)
Dependencies (which tasks must complete first)
Acceptance criteria (what "done" looks like)
Skill (which skill handles this task)

4. Sprint Structure

## Sprint [N]: [Goal]
**Duration**: [X days/weeks]

| # | Task | Size | Depends On | Skill | Status |
|---|------|------|-----------|-------|--------|
| 1 | Create PlayerHealth SO | S | — | uw-scriptable-object-arch | pending |
| 2 | /uw-cmd-implement-feature: damage system (incl. game feel) | M | 1 | uw-game-feel-integrator | pending |
| 3 | /uw-cmd-implement-feature: health UI (incl. animations) | M | 1 | uw-ui-toolkit-binder | pending |
| 4 | Write health edge-case tests | S | 2 | uw-unity-test-runner | pending |

Game feel is embedded inside each /uw-cmd-implement-feature task — not a separate row. If deferred, mark with TODO(gamefeel).

5. Output

Updated docs/SprintPlan.md
If Linear MCP is connected, create tasks in Linear
Task dependency graph (optional)

$ARGUMENTS

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 48 lines · 0 tokens per session scan A 7a5d730a2851

Subscribe to this mod's changes

uw-cmd-plan is a command published in the GitHub repository devdavv/unity-ai-workflow (41 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 430 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Game development Planning ai-workflow antigravity-ide claude-code game-development unity unity2d

uw-cmd-plan

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/uw-cmd-plan — Planning Workflow

Steps

1. Define the Feature

2. Architecture Check

3. Task Breakdown

4. Sprint Structure

5. Output

What this file has done since we first saw it

Other commands, from other repositories

audio-pass

godot-review

ui-flow-review

start-platform

play-dashboard

publish