Individual skill

unity-agentic-workflow

Design, teach, audit, or bootstrap a professional Claude Code and Codex workflow for a Unity repository. Use when deciding which Markdown file owns a rule, writing prompts or slash commands, choosing single-agent versus sequential role handoffs or worktrees, reconciling provider instructions, or finding gaps in an existing Unity agent setup.

plugins/agent-foundry/skills/unity-agentic-workflow/SKILL.md

Read pinned source

Source commit e1a5a792f45899379b42c06e7a332ff40caa7c2f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top