doubt-driven-development
Ensures every significant decision is rigorously challenged before implementation.
What it does
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
Quality judgment
Exceptionally thorough and well-structured: precise non-triviality criteria, explicit when-not-to-use, adversarial prompt, bounded loop, anti-rationalization table, and verification checklist. The cross-model escalation section is somewhat verbose and CLI examples are tool-version-dependent, but the core process is clear and actionable.