doubt-driven-development

# Skill: doubt-driven-development # Adversarial Fresh-Context Review, In-Flight Adapted from [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills) (MIT) — genuinely self-contained, kept close to verbatim. Conceptually complements `comprehension-gate` (a related skill, not installed in this project — it verifies the *human* understands a hard-to-reverse action; this one has the *agent* doubt its own non-trivial decisions before they stand) and `improve`/`tech-lead` (both installed here — those give post-hoc verdicts on a finished artifact; this is in-flight, while course-correction is still cheap). ## Overview A confident answer is not a correct one. Long sessions accumulate context that quietly turns assumptions into "facts" without anyone noticing. Doubt-driven development is the discipline of materializing a fresh-context reviewer — biased to **disprove**, not approve — before any non-trivial output stands. This is not `/review`. `/review` is a verdict on a finished artifact. This is an in-flight posture: non-trivial decisions get cross-examined while course-correction is still cheap. ## When to Use A decision is **non-trivial** when at least one of these is true: - It introduces or modifies branching logic - It crosses a module or service boundary - It asserts a property the type system or compiler cannot verify (thread safety, idempotence, ordering, invariants) - Its correctness depends on context the future reader cannot see - Its blast radius is i...