doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands.
How it works
What doubt-driven-development does
Use it when
Correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
A finished result to review
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about doubt-driven-development
Updated Aug 27, 2026.
What does doubt-driven-development do?
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
Who is doubt-driven-development for?
It is designed for teams that want to hand off recurring work and review the result before it is used.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does doubt-driven-development produce?
A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.
How much does doubt-driven-development cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmtas2snm0063…
- Aug 27, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- addyosmani/agent-skills
- License
- MIT
Connections
Where doubt-driven-development fits
Similar skills2
Security Questionnaire Response
Answer a customer's vendor security questionnaire (SIG, CAIQ, or a custom spreadsheet) from the company's own evidence. Builds and maintains an answer library keyed to control areas, maps each question to policies, SOC 2 report sections, penetration test summaries, and architecture documents, answers Yes, No, Partial, or N/A with a short factual explanation, handles compensating controls honestly, routes answers that need security or legal sign-off, and hands back a gap list for the security owner. Use when a prospect or customer sends a security questionnaire, vendor risk assessment, third-party risk review, or due-diligence form, or needs consistent SIG or CAIQ answers. Do not use for drafting a full RFP response (rfp-response-drafter), writing security policies from scratch, running a security audit or threat model, or negotiating contract terms.FreeSkill · Product and engineeringbrand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.FreeCommunityHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.