Критическая проверка решений через adversarial review

★ 8.7 · testing

doubt-driven-development is a Claude Code skill that subjects every non-trivial decision to fresh-context adversarial review before it stands, using a reviewer biased to disprove rather than approve. The process follows five steps: CLAIM (state the decision and why it matters), EXTRACT (isolate the smallest reviewable artifact plus its contract, stripped of the author's reasoning), DOUBT (invoke a fresh-context reviewer with a verbatim adversarial prompt targeting unstated assumptions, edge cases, hidden coupling, and failure modes), RECONCILE (classify every finding against the artifact), and STOP (exit on trivial findings, three cycles, or explicit user override). Designed strictly for the main-session orchestrator — adding it to a persona's frontmatter is forbidden because it would trigger nested subagent spawning, an anti-pattern prohibited by orchestration-patterns. Use it before committing branching logic, crossing module boundaries, making irreversible production or security-sensitive changes, or asserting properties the type system cannot verify.