Doubt Driven Development
Cross-examine a non-trivial decision with a fresh, adversarial reviewer before it stands, ideally a different model family. Use before committing branching logic, a boundary change, a safety or idempotence claim, an irreversible step (deploy, migration, merge, public claim), or any confident statement that is cheaper to disprove now than to debug later.
Install
/plugin marketplace add frankxai/claude-skills-libraryThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add frankxai/claude-skills-library --skill doubt-driven-developmentgit clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/absorbed/engineering/doubt-driven-development ~/.claude/skills/doubt-driven-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Doubt-driven development Long sessions turn assumptions into facts without anyone noticing. This skill puts a reviewer in front of each non-trivial decision while it is still cheap to change, and points that reviewer at disproving it. It complements the merge gate: `pr-gate` judges the finished PR; doubt-driven checks the decisions on the way there. ## Non-trivial means at least one of - new or changed branching logic; - a module, service or repository boundary is crossed; - a property the compiler cannot check (thread safety, idempotence, ordering, "this is safe", "this scales"); - correctness depends on context a future reader will not see; - the step is hard to undo (deploy, data migration, merge to main, public claim, money path). Skip it for renames, formatting, moves, reading code, running tests, and clear instructions with obvious correctness. ## The cycle 1. **Claim.** Write the decision and why it matters in two or three lines. If you cannot, you have a vibe; settle it first. 2. **Extract.** Isolate the smallest reviewable unit: the diff or function, or the proposal in three to five sentences plus its constraints. Strip your reasoning, keep the evidence, including any caller, guard or test that contradicts you. Over about 300 lines, split it. 3. **Doubt.** Send only the artifact and the contract, never the claim, with an adversarial prompt:
Details
- Skill name
doubt-driven-development- Repository
- frankxai/claude-skills-library
- Path
absorbed/engineering/doubt-driven-development/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Doubt Driven Development skill do?
Cross-examine a non-trivial decision with a fresh, adversarial reviewer before it stands, ideally a different model family. Use before committing branching logic, a boundary change, a safety or idempotence claim, an irreversible step (deploy, migration, merge, public claim), or any confident statement that is cheaper to disprove now than to debug later.
How do I install the Doubt Driven Development skill?
Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Doubt Driven Development popular?
It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.
Related skills
Acos Meta
48frankxai/claude-skills-library
ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.
Acos Visual Gen
48frankxai/claude-skills-library
Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.
Agent Harness Construction
48frankxai/claude-skills-library
Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.
Feynman Thinking
48frankxai/claude-skills-library
Explains a software architecture, algorithm, or control flow in plain language, using a mental model (inputs, transformation, outputs), a text or ASCII flow diagram, and Socratic questions that expose hidden assumptions, then flags needless abstraction. Use when the user asks to explain something simply, "Feynman style", to build a mental model of a system, to explain an architecture to a junior developer, or to challenge a design for over-engineering. Do not use for mechanical edits (renames, typo fixes, formatting, format conversions), boilerplate config, or when the user asks for code only
Brainstorming
430xranx/agentbrief
Design-first approach that generates and evaluates multiple alternatives before coding
Hyperframes CLI
48frankxai/claude-skills-library
HyperFrames CLI dev loop — `npx hyperframes` for scaffolding (init), validation (lint, inspect), preview, render, and environment troubleshooting (doctor, browser, info, upgrade). Use when running any of these commands or troubleshooting the HyperFrames build/render environment. For asset preprocessing commands (`tts`, `transcribe`, `remove-background`), invoke the `hyperframes-media` skill instead.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.