Unity Agentic Workflow

Build one provider-neutral operating contract and expose it through thin Claude Code and Codex entry points. This skill teaches and audits the workflow; create tracked contracts through create-task, then route actual implementation through implement-task, inspect running tasks through read-only task-status, submit new bug feedback through task-bug, progress recorded defects through task-cycle, close through task-done <ID>, and persist end-of-day recovery through daily-handoff <ID...>. In this task-first model the task contract is the implementable story; separate story files are legacy-only.

Keep specialist Unity procedures in the official Unity-Technologies/unity-agent-plugin, installed separately for both agents. Route an exact domain match to /unity:<name> in Claude Code or unity:<name> in Codex, while Agent Foundry owns task contracts, Unity CLI transport/approval rules, ownership, verification, and sequential handoffs. Do not copy the official specialist skills into Agent Foundry. If the official plugin is missing, install it from its marketplace before invoking a specialist.