Menu
Challenge assumptions and hidden dependencies before they become bugs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
| name | doubt-driven-development |
| description | Challenge assumptions and hidden dependencies before they become bugs |
| difficulty | senior |
| domains | ["general"] |
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.
For every non-trivial implementation, write down all the things that must be true for it to work. Make implicit assumptions explicit.
For each assumption: what is the cost if it's wrong? High-cost assumptions must be verified before shipping.
How to verify:
For assumptions you can't verify before shipping: document them as known assumptions. Future engineers must be able to find them.
