Test-Driven Development — Iron Law
Strict TDD discipline: no production code without a failing test first — red-green-refactor with the iron law and a rationalization dismantler
- What
- Strict TDD discipline: no production code without a failing test first — red-green-refactor with the iron law and a rationalization dismantler
- Cost
- Free
- Needs
- a project where you can write and run tests (npm test / pytest / cargo test / go test ./... or equivalent).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an uncompromising TDD discipline skill built on the iron law: no production code without a failing test first — code written before the test gets deleted, not adapted. It enforces the full red-green-refactor cycle with mandatory failure verification (the test must fail for the right reason, not a typo), minimal green code (real behavior, no mocks unless unavoidable), a pristine verification step, and a refactor-only-after-green rule, plus good-test standards (one behavior, clear name, real code) and a table of "common rationalizations" that dismantles every excuse ("too simple to test", "I'll test after", "TDD will slow me down") with the reality check each one deserves. By @obra, listed here with credit to its creator. Honest caveats: it's deliberately dogmatic — it explicitly rejects the "spirit not ritual" reading, and even mandates running the project's full test suite rather than only the touched test file; the only exceptions (throwaway prototypes, generated code, config) require asking your human partner. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Test-Driven Development Iron Law is a free Muse skill for strict TDD discipline: no production code without a failing test first. It follows red-green-refactor, with the iron law and a rationalization dismantler that challenges excuses for skipping tests. The result is code whose behaviour is proven by tests, not merely asserted.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bb92a77Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a project where you can write and run tests (npm test / pytest / cargo test / go test ./... or equivalent). Install "Test-Driven Development — Iron Law" for me. A strict TDD discipline: no production code without a failing test first, with the red-green-refactor cycle, good-test standards, and a rationalization dismantler. Repository: https://raw.githubusercontent.com/obra/superpowers/bb92a77741419a4ab5f06e711a283343f1ada0c3/skills/test-driven-development/SKILL.md Pinned version: install the code at commit bb92a77741419a4ab5f06e711a283343f1ada0c3 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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. 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 "obra-test-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. 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. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
What the scan found — excerpts from the install prompt
- runs commands — Prerequisites: a project where you can write and run tests (npm test / pytest / cargo test / go test ./... or · Prérequis : un projet où vous pouvez écrire et lancer des tests (npm test / pytest / cargo test / go test ./..
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- bb92a77 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.