test-driven-development

An agent skill by obra, from obra/superpowers. Tags: api, developer-tools, web.

What it does

Use when implementing any feature or bugfix, before writing implementation code

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add obra/superpowers --skill test-driven-development

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/obra/superpowers
cp -r superpowers/skills/test-driven-development ~/.claude/skills/test-driven-development

Safety box score

Not rated yet. A safety box score grades what a skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. Anyone can request one from this page; it is saved for everyone. How the score works.

Source

Repository

obra/superpowers (all skills from this repository)

Path

skills/test-driven-development/SKILL.md

Branch

main

Updated

2026-09-19

Related skills

• executing-plans — Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution.
• finishing-a-development-branch — Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
• receiving-code-review — Use when receiving code review feedback, before implementing suggestions.
• requesting-code-review — Use when completing tasks, implementing major features, or before merging to verify work meets requirements
• systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
• using-git-worktrees — Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via.