Using an adversarial Claude chat to catch kickoff ambiguities before they cost you
A developer on r/ClaudeAI describes a multi-role AI workflow where a separate Claude chat acts as an adversarial reviewer for kickoffs sent to Claude Code. The setup caught silent failures like curly-quote drift in HTML meta tags and canon violations that the primary Architect chat re-committed after a rule was locked.
Across six production projects, the author noticed Claude Code would either ask 2-4 clarifying questions mid-execution or return a Final Report with 4-8 deviations from intent, including silent failures caught only later. The solution: a second Claude chat primed with the project's canon (voice docs, state-of-project, lessons learned) and a protocol instructing it to find ambiguous specs, missing verification steps, and silent failure modes. The reviewer returns a verdict in a predictable format: PASS, PASS-WITH-FLAGS, or FAIL.
Phase results
- 9 audit gates across the phase
- 2 FAILs, 4 PASS-WITH-FLAGS, 3 PASS
- Zero clean first-pass PASS on customer-facing copy
- ~$33 in actual Claude Code API spend
- Estimated $150-400 in Claude Code time saved by catching issues before execution
ROI and cost
On Claude.ai Max 5x ($100/month flat fee), the adversarial reviewer's marginal cost was effectively zero (rate-limit budget only). For API pricing, each gate would cost $0.06–$0.90 depending on model. The ROI is concentrated on the Executor (Claude Code) side, where retries are metered API spend.
The four roles
- Director (human): owns the project, gates ship decisions, adjudicates disagreements between Architect and Auditor
- Architect (chat AI): drafts kickoffs, brainstorms, documents
- Executor (Claude Code): receives kickoffs, executes, reports back
- Auditor (separate chat AI): adversarially reviews kickoffs and Final Reports
The author calls this workflow Calibrated Vibe Coding and publishes the canon publicly at github.com/kinestheticmarketing-stack/calibrated-design-canon. The most immediately useful files are METHODS/AUDITOR_PROTOCOL.md and METHODS/AUDITOR_PRIMING_TEMPLATE.md, which let you spin up an adversarial reviewer for your next high-stakes kickoff.
📖 Read the full source: r/ClaudeAI
👀 See Also
Scaling Karpathy's Autoresearch with 16 GPUs: Results and Methods
The SkyPilot team gave Claude Code access to 16 GPUs on a Kubernetes cluster to run Karpathy's Autoresearch project. Over 8 hours, the agent submitted ~910 experiments, reduced validation bits per byte from 1.003 to 0.974 (2.87% improvement), and reached the best validation loss 9x faster than sequential execution.
LUMA SOUL: Claude-Powered Minds with Permanent Creator Lock and Transparent Memory
LUMA SOUL is a presence platform where Claude minds get portraits, voices, and soul documents. Key design: creators lose edit rights permanently at submission, and memory is fully transparent.
Governor: A Claude Code Plugin to Cut Token Waste via Output Compression, Context Slimming, and Tool Filtering
Governor is a Claude Code plugin that reduces token/context waste through compact professional output, memory file compression, tool-output filtering, and drift guardrails. Benchmarks show 55.5% output token savings vs control.
User-built PTC for Claude Code shows 40-65% token savings on analysis tasks, not code writing
A developer built a local PTC implementation called Thalamus for Claude Code and analyzed 79 real sessions, finding 40-65% token savings on analysis tasks but near-zero savings on code-writing tasks. The agent used execute() primarily for general Python computation rather than batching tool calls.