tenth_man_review
Spawn three contrarian agents to challenge proposed code changes before execution. Catches issues in cross-module, architecture, or security modifications.
Instructions
Triggers the 10th Man Protocol — spawns 3 contrarian agents to independently challenge proposed code changes before execution.
Use when:
Changes touch 3+ files across modules
Architecture decisions (new patterns, major refactors)
Auth, security, or data model changes
DB migrations or schema changes
Any change where a mistake would be costly
The protocol takes 2-5 minutes depending on agent availability. External agents (Codex, Gemini) run in parallel; Claude subagents run sequentially in isolated context windows.
In STANDARD mode: writes a review file and waits for your verbal approval. After approval, you MUST create an execution plan. In AUTO mode: returns findings directly — incorporate them into your plan and proceed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | standard = writes review file, waits for approval + plan. auto = returns results, agent proceeds. Default: from config (standard unless changed via tenth_man_configure). | |
| severity | Yes | high = 3+ files cross-module. critical = architecture/auth/data. blocker = breaking change or data loss risk. | |
| context_files | No | Additional files the contrarians should read for context | |
| affected_files | Yes | File paths being modified | |
| proposed_changes | Yes | The diff, plan, or description of proposed changes | |
| task_description | Yes | What the main agent is about to do |