Subagent Review Flow

A review should lead to a clear resolution, not stop at a list of findings.

This skill helps a coordinating agent work with one or more reviewer subagents, verify their findings, and resolve disagreements through evidence. It treats review as a complete workflow, from independent assessment through fixes and final verification, rather than a one-off exchange of feedback.

Bound the Review

The calling workflow determines whether a review is required, what it examines, which reviewers participate, and which effects are authorized. This skill doesn’t add a review checkpoint. The execution interface owns dispatch, monitoring, and session mechanics.

The coordinator owns the shared review record, findings validation, and integration. A review-only task remains read-only. During authorized implementation, continue through resolution only for corrections covered by the existing task authority.

When acting as a reviewer, evaluate the assigned target independently and follow the reporting requirements. On follow-up, assess the selected follow-up scope using the evidence criteria in Resolve Disagreements. Explain whether each finding under reassessment remains standing and why. You own that status in your reviewer thread. Leave coordination to the coordinator.

Prepare the Review

Keep one conversation-local review record: baseline first, then scope and exclusions, settled decisions, and current finding classifications. For each reviewer, track the session, latest reviewed state, and standing findings. Use a shared starting baseline for a group of reviewers.

Give a first-pass reviewer the minimum neutral context needed to evaluate the target: baseline, scope and exclusions, intended behavior, applicable instructions, execution boundaries, and material evidence limitations. Don’t front-load coordinator conclusions, self-assessment, anticipated findings, implementation defenses, or decision history unless needed to establish a governing requirement or the expressly requested review subject. Don’t withhold safety or authority requirements, the actual requested subject, or evidence needed to evaluate it. Keep other decision history with the coordinator rather than forwarding it automatically.