doubt-driven-development SKILL.md skillA
doubt-driven-development in addyosmani/agent-skills is at git:20261029.c55b842 (Oct 29, 2026), graded A.
mdr add addyosmani/agent-skills/doubt-driven-development@git:20261029.c55b842This copy is 1 version behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
doubt-driven-development from vraj-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vraj-ai/skills
- Path
third-party/addyosmani/skills/doubt-driven-development/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261014.242e75d, committed Oct 14, 2026
- Size
- 16,647 bytes
- Repository stars
- 3
- License
- MIT
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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")
…Read the whole file at its exact version.
How to install
mdr add vraj-ai/skills/doubt-driven-development@git:20261014.242e75dPins git:20261014.242e75d in mdr.lock, 1 version behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jbzg2dyz5vulf5iz/6fa1fcd8420c28daf7e53c5b08b0f20b907911efd2a6d9bce0b9740da20a4008.json
Then /plugin install doubt-driven-development@markdownregistry-jbzg2dyz5vulf5iz in Claude Code. It installs git:20261014.242e75d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/doubt-driven-development@sha256:6fa1fcd8420c28daThe older copy line above pins the label git:20261014.242e75d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jbzg2dyz5vulf5iz)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest addyosmani/agent-skills/doubt-driven-development, and what changed since 6fa1fcd? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of doubt-driven-development from somewhere else? Ask it: where did my doubt-driven-development come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20261029.c55b842 of doubt-driven-development in addyosmani/agent-skills (skills/doubt-driven-development/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260907.cda4542, which it committed on Sep 7, 2026, before this repository did; graded A, 1 version behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/doubt-driven-development/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16647 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vraj-ai/skills · 3 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jbzg2dyz5vulf5iz GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/doubt-driven-development GET https://markdownregistry.com/api/v1/blob/6fa1fcd8420c28daf7e53c5b08b0f20b907911efd2a6d9bce0b9740da20a4008
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.