doubt-driven-development

Subjects non-trivial decisions to adversarial fresh-context review before they stand.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill doubt-driven-development-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doubt-driven-development
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/doubt-driven-development
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill doubt-driven-development-raishoemi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confident answers are not always correct ones, and long sessions quietly turn assumptions into facts. This Skill catches wrong decisions early by forcing every non-trivial decision through an adversarial fresh-context review while course-correction is still cheap. ## Core Features & Use Cases - Five-step doubt cycle: CLAIM the decision, EXTRACT the smallest reviewable artifact plus contract, DOUBT it with an adversarial fresh-context reviewer, RECONCILE findings by precedence, and STOP at a bounded condition (trivial findings, 3 cycles, or user override). - Cross-model escalation: In interactive sessions, always offers a second opinion via external CLIs such as Gemini or Codex, with PATH checks, read-only sandboxing, and stdin piping to avoid shell injection. - Use Case: Before committing a new caching layer claimed to be thread-safe, extract the diff and its contract, spawn an adversarial reviewer instructed to find issues rather than validate, classify each finding as contract misread, actionable, trade-off, or noise, and iterate until the stop condition is met. ## Quick Start Ask the agent to apply doubt-driven development to review the architectural decision in your current change before committing it.

Frequently Asked Questions about doubt-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a code decision before committing it?

Use the doubt cycle: write a compact CLAIM, extract the artifact and its contract without your reasoning, then spawn a fresh-context reviewer with an adversarial prompt that finds issues rather than validating. Classify each finding and iterate up to three cycles.

What is the difference between doubt-driven development and code review?

Doubt-driven development is an in-flight posture applied per non-trivial decision while changes are still cheap to reverse. A code review or /review pass is a post-hoc verdict on a finished artifact, so the two are complementary rather than interchangeable.

When should I not use adversarial review on my changes?

Skip it for mechanical operations like renaming or formatting, one-line changes with obvious correctness, reading or summarizing code, pure tooling operations, and when the user explicitly prioritizes speed over verification.

Can this skill run inside a subagent or persona context?

No, it is designed for the main-session orchestrator because personas must not spawn other personas. Inside a subagent, escalate to the main session, or as a last resort use a degraded self-questioning fallback flagged as not fresh-context.

How does cross-model review work with Gemini or Codex CLI?

In interactive sessions the agent always offers a cross-model second opinion. It verifies the binary works, confirms the exact invocation with the user, writes the prompt to a file, and pipes it via stdin using a read-only sandbox to prevent shell injection.

Why does the reviewer only receive the artifact and contract?

Passing the CLAIM or the author's reasoning biases the reviewer toward agreement. The reviewer must independently determine whether the artifact satisfies the contract, so only ARTIFACT and CONTRACT are provided.