cross-reviewlisted
Install: claude install-skill ShlomiPorush/agent-skills
# Cross review
One main agent owns the work, the decisions, and the report to the user. A partner agent from the other provider reviews the plan, the result, or both, through T3 Code's `delegate_task`. Partner agreement never replaces the user's approval.
This skill needs an agent running inside a T3 Code thread with the `t3-code` MCP tools. Outside T3, say that cross review is unavailable and continue solo.
## Choose the tier
Risk beats the type of work at every tier.
| Tier | When | Partner does |
|---|---|---|
| Solo | A spot task with limited, clear impact. | Nothing. |
| Review-only | Bug fixes and medium code changes. | Reviews the result. |
| Full | Anything that needs a plan under the "substantial work, plan first" rule. Always, even when tiny: security, auth, migrations, data deletion, irreversible actions, CI or release, public API, and changes to agent instructions or skills. | Reviews the plan, then the result. |
The user's words win over the table: "without partner" means Solo, and "with partner" means at least Review-only.
## Order of work
- Review-only: execute, run the budget gate, partner reviews the result, fix, report.
- Full: write the plan, run the budget gate, partner reviews the plan, revise it, present the revised plan to the user when approval is needed, execute, run the budget gate again, partner reviews the result, fix, report.
Run the gate before every `delegate_task` call, not once per task. Plan and result reviews can be hours apart.
Wh