test-driven-development SKILL.md skillA
test-driven-development from brunob54/superpowers-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add brunob54/superpowers-orchestrator/test-driven-development@git:20261021.eed7347Pins git:20261021.eed7347 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- brunob54/superpowers-orchestrator
- Path
skills/test-driven-development/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261021.eed7347, committed Oct 21, 2026
- First version recorded
- Mar 8, 2026
- Size
- 5,941 bytes
- Repository stars
- 3
- License
- MIT
MUST USE for any behavior change: write failing tests before production code. No exceptions. Triggers on: "TDD", "write tests first", any implementation task, bug fix needing regression tests, behavior changes during execution. Routed by using-superpowers, or invoke directly via /test-driven-development.
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
# Test-Driven Development Write failing tests first. Then write minimal code to pass. ## Iron Law **No production code before a failing test proves the behavior is missing.** If code was written first, **delete it** and restart from a test. No exceptions. This is the hardest rule to follow and the most important. Every rationalization to skip it leads to untested behavior that breaks later. ## Cycle 1. **RED**: Write one small failing test for one behavior. 2. **VERIFY RED**: Run the test. Confirm it fails **for the expected reason** (not a syntax error or import issue). 3. **GREEN**: Write the **minimum** production code to make the test pass. Nothing more. 4. **VERIFY GREEN**: Run the target test and relevant broader tests. Confirm pass. 5. **REFACTOR**: Improve structure without changing behavior. Tests must stay green. Repeat per behavior. Never skip VERIFY steps. ## Test Infrastructure Check Before writing the first test, verify the project has a test runner: 1. Check for test config: `jest.config.*`, `vitest.config.*`, `pytest.ini`, `pyproject.toml [tool.pytest]`, `go.mod`, `Cargo.toml`, `.rspec`, `phpunit.xml` …
Read the whole file at its exact version.
How to install
mdr add brunob54/superpowers-orchestrator/test-driven-development@sha256:f94f5e64352672abThe line at the top of this page pins the label git:20261021.eed7347, 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_x2weajdcj3wh5gfo)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Mar 8, 2026 and Oct 21, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.eed7347 latest | 2026-10-21 | eed7347 | 5,941 B | A | view · diff |
| git:20260415.0a78a70 | 2026-04-15 | 0a78a70 | 5,315 B | A | view · diff |
| git:20260313.623081f | 2026-03-13 | 623081f | 4,521 B | A | view · diff |
| git:20260308.5884b95 | 2026-03-08 | 5884b95 | 3,652 B | A | view · diff |
| git:20260308.f9b9480 | 2026-03-08 | f9b9480 | 3,556 B | A | view · diff |
| git:20260308.eb8b7c1 | 2026-03-08 | eb8b7c1 | 1,926 B | A | view |
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 (5941 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
brunob54/superpowers-orchestrator · 3 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x2weajdcj3wh5gfo GET https://markdownregistry.com/api/v1/resolve?ref=brunob54/superpowers-orchestrator/test-driven-development GET https://markdownregistry.com/api/v1/blob/f94f5e64352672ab122740f386c2845751ea3a626aed3453ef6edc2aba12b215
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.
More from brunob54/superpowers-orchestrator
Every file in brunob54/superpowers-orchestrator