Doubt driven development
Skill sohaibdevv/AI-AGENT-SKILLS/skills/doubt-driven-development
Challenge assumptions and hidden dependencies before they become bugsFrom its SKILL.md
npx -y skills add sohaibdevv/AI-AGENT-SKILLS --skill doubt-driven-developmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 278 tokens by cl100k_base, as published. Nobody here has run it
Overview
Every "I'm sure this is fine" is a future incident. This skill applies systematic skepticism to assumptions in requirements, implementations, and integrations before they ship.
When to Use
- When something "seems obvious" but hasn't been verified
- When implementing code that depends on external behavior
- When code review reveals an implicit assumption
- When debugging a "that's impossible" bug
Process
Step 1: List your assumptions
For every non-trivial implementation, write down all the things that must be true for it to work. Make implicit assumptions explicit.
Step 2: Classify by risk
For each assumption: what is the cost if it's wrong? High-cost assumptions must be verified before shipping.
Step 3: Verify high-cost assumptions
How to verify:
- Write a test that fails if the assumption is wrong
- Find the source of truth (spec, documentation)
- Measure it (add a log, run a query)
- Ask someone who knows
Step 4: Make remaining assumptions visible
For assumptions you can't verify before shipping: document them as known assumptions. Future engineers must be able to find them.
Verification Requirements
- All non-trivial assumptions listed
- High-cost assumptions verified before shipping
- Remaining assumptions documented in code