Dual Verifier

Overview

A post-implementation review skill that dispatches two independent subagents to verify a completed task. Both agents run the same verification checks without seeing each other's work. Their findings are then merged into one report — with each finding tagged by which agent(s) caught it.

Core principle: One agent can miss things, hallucinate, or rubber-stamp a summary. Two agents working independently catch more issues and — more importantly — when they disagree on a finding, that disagreement is itself a signal worth investigating.

This is NOT just running the same check twice. The value is independence: each agent must form its own picture of what was actually done by reading the code, the diff, and the test output — not by trusting any summary it was given.

When to Use

• After an implementation task is complete and the user asks for verification
• Before a commit, PR, or hand-off where over-claiming would cost
• When a previous Claude session said "done" and the user is skeptical
• When the user explicitly invokes a verification slash command