doubt-driven-development

doubt-driven-development is a skill for Claude Code, Codex from jcarlosrodicio/opencode-agent-orchestration-kit. It costs 67 tokens per session (1,808 once invoked), scanned A, original, Apache-2.0.

A review practice that asks a fresh reviewer to challenge each non-trivial decision before it is accepted. It is used during the work, rather than only after the finished code is reviewed.

In plain words
What is it for?
Use it to question architecture choices, branching logic, module or service boundaries, safety claims, and other decisions whose correctness is not fully checked by the compiler.
Why use it?
It catches unsupported assumptions while changes are still easy to make, especially in unfamiliar, security-sensitive, production, or irreversible work.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jcarlosrodicio/opencode-agent-orchestration-kit/doubt-driven-development
Any agent
npx skills add jcarlosrodicio/opencode-agent-orchestration-kit --skill doubt-driven-development
Clone the repo
git clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doubt-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/doubt-driven-development.svg)](https://agentmods.dev/skills/jcarlosrodicio/opencode-agent-orchestration-kit/doubt-driven-development)
Your own site
<a href="https://agentmods.dev/skills/jcarlosrodicio/opencode-agent-orchestration-kit/doubt-driven-development"><img src="https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/doubt-driven-development.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,808 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.01808
Opus 5 $0.00034 $0.00904
Sonnet 5 $0.00013 $0.00362
Haiku 4.5 $0.00007 $0.00181

Measured 4d ago against content hash 45b89c102f41, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doubt-driven-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

opencode/skills/doubt-driven-development/SKILL.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Doubt-Driven Development

Overview

A confident answer is not a correct one. Long sessions accumulate context that quietly turns assumptions into "facts" without anyone noticing. Doubt-driven development is the discipline of materializing a fresh-context reviewer — biased to disprove, not approve — before any non-trivial output stands.

This is not /review. /review is a verdict on a finished artifact. This is an in-flight posture: non-trivial decisions get cross-examined while course-correction is still cheap.

When to Use

A decision is non-trivial when at least one of these is true:

  • It introduces or modifies branching logic
  • It crosses a module or service boundary
  • It asserts a property the type system or compiler cannot verify (thread safety, idempotence, ordering, invariants)
  • Its correctness depends on context the future reader cannot see
  • Its blast radius is irreversible (production deploy, data migration, public API change)

Apply the skill when:

  • About to make an architectural decision under uncertainty
  • About to commit non-trivial code
  • About to claim a non-obvious fact ("this is safe", "this scales", "this matches the spec")
  • Working in code you don't fully understand

When NOT to use:

  • Mechanical operations (renaming, formatting, file moves)
  • Following a clear, unambiguous user instruction
  • Reading or summarizing existing code
  • One-line changes with obvious correctness
  • Pure tooling operations (running tests, listing files)
  • The user has explicitly asked for speed over verification

If you doubt every keystroke, you ship nothing. The skill applies only to non-trivial decisions as defined above.

The Process

Step 1: CLAIM — Surface what stands

Name the decision in two or three lines:

CLAIM: "The new caching layer is thread-safe under the
        read-heavy workload described in the spec."
WHY THIS MATTERS: a race here corrupts user data and is
                  hard to detect in QA.

If you can't write the claim that compactly, you have a vibe, not a decision. Surface it before scrutinizing it.

Read the full file on GitHub · 169 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 169 lines · 67 tokens per session scan A 45b89c102f41

Subscribe to this mod's changes

doubt-driven-development is a skill published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 5d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,808 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

qa

Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…

arcee-ai/nac · 100 tokens

release

Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.

arcee-ai/nac · 53 tokens

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

ahk-review

Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.

enmanuelmag/agent-harness-kit · 35 tokens

ahk-consultant

Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.

enmanuelmag/agent-harness-kit · 35 tokens

ahk-triage

Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.

enmanuelmag/agent-harness-kit · 29 tokens