doubt-driven-developmentlisted
Install: claude install-skill yjhqwer/yjh-discipline
# Doubt-Driven Development
A decision that was never attacked is not validated — it is untested. Before a non-trivial decision becomes the plan, a fresh-context reviewer whose only job is to prove it wrong gets one swing at it.
## When it fires
Any of:
- the change modifies branching logic
- it crosses a module or service boundary
- it asserts a property no compiler or type-checker can verify
- it depends on context the decision-maker cannot see
- its blast radius is irreversible (production auth, security-sensitive logic, data migration, public-facing actions)
- a prior-art verdict (Adopt / Extend / Compose / Build) is about to be recorded
## When it stays silent (exclusions)
Mechanical operations; changes the user explicitly prescribed; reading and summarizing; one-line obvious changes; pure tooling work; and any time the user has chosen speed over verification. When "non-trivial" is genuinely unclear, the cost asymmetry decides: a refutation run costs minutes, debugging a confident wrong decision costs hours.
## Procedure
1. **FRAME** — Write the decision as an **ARTIFACT** (the plan, design, or verdict itself) plus a **CONTRACT** (the acceptance criteria it must meet). The artifact never travels with the author's reasoning or self-defense.
2. **REFUTE** — Dispatch a fresh-context subagent with the artifact and contract only:
> Adversarial review. Find what is wrong with this artifact. Assume the author is overconfident. Check it against the contract only. Do N