Localized reading guide
test-driven-developmentPurpose, usage and source
Use when implementing any feature or bugfix, before writing implementation code
Source retrieved:
- Source repository
- obra/superpowers
- SKILL.md
skills/test-driven-development/SKILL.md- Repository stars
- 309,479
- Repository updated
- 2026-10-30
- Categories
- Development
- Last collected
License: MIT
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Use when implementing any feature or bugfix, before writing implementation code
How the upstream workflow works
Overview
Write the test first. Watch it fail. Write minimal code to pass. Core principle: If you didn't watch the test fail, you don't know if it tests the right thing. Violating the letter of the rules is violating the spirit of the rules.
Upstream passage · L8 ↗When to Use
Exceptions (ask your human partner): Thinking "skip TDD just this once"? Stop. That's rationalization.
Upstream passage · L16 ↗The Iron Law
Write code before the test? Delete it. Start over. Don't keep it as "reference"
Upstream passage · L31 ↗NO PRODUCTION CODE WITHOUT A FAILING TEST FIRSTRequirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2ce8aa15d05bd57213e6f746f953aafb7ded7a8b- Source SHA-256
64b03fce4aee5a97a93160cea8111f3ba13a17b7c001db4bd5836d67fd10705d