Adversarial Bug Hunt Pipeline

Run a 3-phase adversarial bug hunting pipeline using context-isolated subagents. Each phase runs in a fresh context to prevent bias contamination.

Phase Overview

1. Bug Hunter — Aggressively scans codebase for all potential bugs, scored by severity
2. Bug Skeptic — Attempts to disprove each reported bug with counter-evidence
3. Bug Arbiter — Weighs both arguments and delivers final verdicts

Determine Scope

Before launching Phase 1, determine the target scope:

• If the user specified files or directories, use those exact paths
• If invoked in a project context with no specific scope, scan the full codebase
• Use Glob to verify the target paths exist

Store the resolved scope as a comma-separated list of paths for passing to subagents.