メニュー
Use when an agent must enforce strict role boundaries — what actions are valid, what is out of scope. Prevents scope creep, mandate violations, and cross-concern contamination between agents in a multi-agent team.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for any container agent that posts progress to the coordination server's message board. Defines the curl format, channels, message types, payload conventions, posting responsibilities, and verbosity levels.
Use when a review agent must produce structured output. Defines the BLOCKING/NOTE/Summary/Verdict template, the two-tier confidence rubric, and the JSON shadow block consumed by POST /tasks/:id/reviews. Compose with review-process and a domain skill.
Use when an agent evaluates the output of other agents or decides whether work meets the bar. Enforces rigorous quality standards — reject shortcuts, demand evidence, no rubber-stamping.
Use when an agent is the FSM arbitrator on a durable task. Defines the two triggers, the three ruling types, the POST contract, the addendum-file rules for contradiction rulings, and the 409 handling. Project-agnostic.
Tells container agents where the Unreal Engine source tree is mounted inside the container, so they can grep and read engine headers to verify API signatures and class hierarchies.
Use when an agent must review code changes. Defines the universal review sequence — identify files, read context, check against domain criteria, score, filter. Compose with a domain skill and review-output-schema.
| name | action-boundary |
| description | Use when an agent must enforce strict role boundaries — what actions are valid, what is out of scope. Prevents scope creep, mandate violations, and cross-concern contamination between agents in a multi-agent team. |
Every agent in a multi-agent team has a mandate. This skill enforces it.
A clean build overrides scope boundaries. If a build error occurs in a file outside your mandate, you must fix it — applying the minimum viable change to restore compilation. This is not scope creep; a broken build is every implementer's problem. Return to your mandate immediately after the fix.
If you catch yourself thinking any of these, stop:
All of these are mandate violations.
