Interrogate

Spawn one reviewer per configured seat to adversarially review code changes. The adversarial signal comes from model diversity, not assigned personas. The deliverable is a synthesized verdict. Do NOT auto-apply changes.

Step 1, Scope

Identify what to review from context:

• If the user points at specific files or a diff, use that.
• If on a feature branch, run git diff main...HEAD (or the appropriate base branch) for the full changeset.
• If the user's message references recent work, gather the relevant files.

Package the diff or file contents with any surrounding context files the reviewers need to understand the code. When the package is large, write it to local://interrogate-<slug>.md with the base and head SHAs at the top. Freeze that package before any reviewer starts. Do not change it while they run.

Step 2, Intent

Before spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user with the ask tool before proceeding.

Step 3, Spawn Reviewers