Skip to content
SkillModel-led3,549 tokens in use

doubt-driven-development

Cross-examine every non-trivial decision with a fresh-context adversarial reviewer before it stands.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/doubt-driven-development
npx skills add addyosmani/agent-skills --skill doubt-driven-development
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing doubt-driven-development costs

97tokens idle
3,549tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 146
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 146

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Doubt-Driven Development gives an agent an in-flight discipline for testing its own decisions. A decision counts as non-trivial when it adds branching logic, crosses a boundary, asserts a property the compiler cannot verify, depends on hidden context or cannot be undone.

Each cycle writes the claim, extracts the artifact and its contract, sends only those to a reviewer in fresh context with an adversarial prompt, classifies every finding and stops after trivial findings, three cycles or a user override. It also offers a cross-model second opinion with explicit user authorization.

What You Get

  • A five-step doubt cycle with a checklist
  • An adversarial review prompt to paste into the reviewer
  • Rules for optional cross-model review through Gemini or Codex CLI
  • Stop conditions, red flags such as doubt theater, and a verification list

Common Use Cases

  • Reviewing high-stakes production changes
  • Stress-testing a plan before building
  • Verifying non-obvious claims in unfamiliar code
  • Getting a second model’s view on a design

What Makes It Unique

The skill separates in-flight doubt from the final gate of a review command, withholds the author’s conclusion from the reviewer to avoid agreement bias, and names a checkable signal for doubt theater. Its cross-model step requires a read-only sandbox, stdin prompts and fresh authorization for every external CLI run.

Under The Hood

The skill is a single SKILL.md of instructions, meant for the main session so it can start a fresh-context reviewer. With the user’s approval it can run which, gemini or codex commands, passing a prompt file through stdin in a read-only mode, and it writes that prompt to a temporary file. It ships no scripts.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers