SKILL.md
do-and-judge
Task
Execute a single task by dispatching an implementation sub-agent, verifying with an independent judge, and iterating with feedback until passing or max retries exceeded.
Arguments
| Argument | Format | Default | Description |
|---|---|---|---|
task |
Free-form text | Required | Task description to execute |
--model |
haiku|sonnet|opus |
auto-selected | Explicit user override for all sub-agents: implementation, meta-judge, and judge. When omitted, you MUST select the model per the Model Selection Policy — there is no fixed fallback tier. When provided, the user's choice wins over the policy for every sub-agent — see the Escalation Rule for how escalation interacts with an explicit override. |
--strict |
--strict |
false |
Disable the Iteration Discretion Rule - the task passes ONLY when score >= 4.0, otherwise retry until max retries is reached. |
Example: /do-and-judge Refactor the UserService class to use dependency injection --strict
Context
This command implements a single-task execution pattern with meta-judge → LLM-as-a-judge verification. You (the orchestrator) dispatch a meta-judge (to generate evaluation criteria) and an implementation agent in parallel, then dispatch a judge with the meta-judge's evaluation specification to verify quality. If verification fails, you launch new implementation agent with judge feedback and iterate until passing (score ≥4, or accepted per the Iteration Discretion Rule) or max retries (3) exceeded.
Key benefits: