back
loading skill details...
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in…
Doubt-Driven Development 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 irreversible (production deploy, data migration, public API change) Apply the skill when:
don't have the plugin yet? install it then click "run inline in claude" again.