unity-game-development-agent-verification

name

unity-game-development-agent-verification

description

Verify Unity game-development agent work and the unity-game-development-agent skill package. Use this whenever reviewing Unity agent outputs, checking whether a Unity project was safely inspected or modified, validating playable-slice claims, auditing scene/prefab/reference risk, or deciding whether a Unity skill package has enough files, references, scripts, templates, evals, and proof gates for a novice agent.

Unity Game Development Agent Verification

Purpose

Use this skill to audit Unity agent work with a proof-first mindset. The agent being verified may be overconfident, Unity-naive, or working without Editor access. Your job is to separate real evidence from narration.

This skill verifies two things:

• The unity-game-development-agent skill package is complete enough to guide a confused agent.
• Unity project changes made under that skill are safe, validated, and playtest-oriented.

When to Use

Use this skill when:

• The user asks for an audit, review, verification, critique, or readiness check of Unity agent work.
• A Unity skill package was created or modified.
• A Unity project was edited by an agent.
• The agent claimed compile/playtest/build success.
• The task involved scene, prefab, serialized reference, .meta, package, or build-setting risk.

Verification Stance

Assume claims are unproven until backed by files, logs, commands, screenshots, Unity MCP output, test results, build artifacts, or a repeatable audit report.

Do not accept:

• "Should work."
• "Likely compiles."
• "I improved the scene" without before/after evidence.
• "Build succeeded" without command, log, artifact path, and exit status.
• C# scripts added without scene wiring when the user asked for a playable game.

Package Audit

For the unity-game-development-agent skill package, require:

• SKILL.md with clear trigger description and resource routing.
• AUDIT.md explaining prior gaps and current correction.
• scripts/unity_project_audit.py.
• References for project anatomy, inspection, creation, CLI validation, scene/prefab safety, gameplay systems, visual/UI/audio work, recovery, and sources.
• References for validation evidence levels, compatibility, and optional-tool contracts.
• Templates for work-cycle report, playtest checklist, vertical-slice plan, component split, gitignore, active-scene snapshot, build-scene validator, and vertical-slice bootstrap.
• evals/evals.json with realistic Unity tasks and objective assertions.
• Packaged .skill file if packaging is requested.

Run:

python3 <this-skill>/scripts/verify_unity_skill_package.py <path-to-unity-game-development-agent-skill>

Unity Work Audit

For a Unity project change, require evidence for:

• Project root markers: Assets/, ProjectSettings/, Packages/.
• Unity version.
• Package manifest.
• Git state before/after.
• Main scene.
• Highest evidence level reached; compile, scene, play-mode, test, and build claims must remain separate.
• Scene/prefab/reference status.
• Changed files.
• Validation commands/tools.
• Playable loop status.
• Known issues and next work.

If Unity is unavailable, static audit is acceptable but runtime claims are not.

Playable Slice Criteria

A created slice must include:

• Main scene.
• Player movement.
• Camera.
• Objective/win condition.
• Interaction or pickup.
• Enemy/hazard/pressure if requested.
• HUD objective/status.
• Restart/pause or documented blocker.
• Feedback hooks.
• Visual composition and readable materials/lighting.
• Validation report.

Scripts alone do not count as a playable Unity game.

Scene/Prefab Safety Criteria

For scene or prefab work, verify:

• Unity-aware tools or editor scripts were preferred.
• Direct YAML edits were minimal and justified.
• .meta files were preserved.
• Serialized field renames used a migration strategy when needed.
• Colliders, triggers, spawn points, build settings, and object references were preserved.
• Missing scripts/references were checked.

Report Format

Verification result:
- Status: pass / partial / fail
- Scope:
- Evidence reviewed:

Findings:
- [severity] [file/path] - [issue]

Validation:
- Commands/tools checked:
- Evidence that passed:
- Evidence missing:

Playable status:
- Compile:
- Main scene:
- Player loop:
- Objective loop:
- UI/feedback:
- Build/playtest:

Required fixes:
- [fix]

Next verification:
- [next check]

Pass Bar

Pass only when claims are evidenced and the project/package can be handed to a fresh agent without hidden assumptions.