メニュー
Use when an agent implements code via TDD and must report results. Defines the input shape (plan or fix instructions) and the output template (Changes Made, Build Status, Test Status, Notes).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tdd-implementation-io-schema |
| description | Use when an agent implements code via TDD and must report results. Defines the input shape (plan or fix instructions) and the output template (Changes Made, Build Status, Test Status, Notes). |
| axis | schema |
Standard input and output format for TDD implementation agents.
You receive either:
## Changes Made
For each file touched:
- **File**: path
- **Action**: created / modified / deleted
- **What changed**: brief description
## Build Status
- **Result**: SUCCESS / FAILURE
- **Command**: <build command used>
- **Errors** (if failed): <relevant error output>
## Test Status
- **Result**: PASS / FAIL / SKIP (reason)
- **Command**: <test command used>
- **Tests**: N passed, N failed
- **Failures** (if any): <failing test names and assertion errors>
## Notes
Anything noteworthy (trade-offs made, deviations from plan with justification).
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.