Doubt-Driven Development
Cross-examine every non-trivial decision with a fresh-context adversarial reviewer
- What
- Cross-examine every non-trivial decision with a fresh-context adversarial reviewer
- Cost
- Free
- Needs
- none beyond a working agent; designed for a main-session orchestrator that can spawn a fresh-context reviewer
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an in-flight adversarial review discipline: before any non-trivial decision stands (branching logic, module boundaries, unverifiable invariants, irreversible operations), materialize a fresh-context reviewer biased to disprove, not approve. Long sessions quietly turn assumptions into "facts" — this skill catches them while course-correction is still cheap. A decision is non-trivial when it crosses a module boundary, asserts something the type system can't verify, or has an irreversible blast radius. Distinct from a finished-artifact /review: this is a posture applied during the work, not a verdict after it. By @addyosmani, listed here with credit to its creator. Honest caveats: designed for the main-session orchestrator that can spawn a fresh-context reviewer — inside a subagent context (no nested spawns) it degrades to self-questioning or should be surfaced to the user; and doubting every keystroke ships nothing — it applies only to non-trivial decisions as defined. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none beyond a working agent; designed for a main-session orchestrator that can spawn a fresh-context reviewer Install "Doubt-Driven Development" for me. Cross-examine every non-trivial decision with a fresh-context adversarial reviewer Repository: https://github.com/addyosmani/agent-skills/blob/main/skills/doubt-driven-development/SKILL.md 1. Fetch the SKILL.md file for the addyosmani-doubt-driven-development skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-doubt-driven-development". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.