test-driven-development

by obra/superpowers · Coding & Development

Enforces test-driven development by writing a failing test first, then minimal implementation code, then refactoring, for every feature or bugfix.

Lift-13ppscreen tier · directional

Trustsecurity · quality · license · upkeep

Scan Saferisk 0/100

LicenseMITserved via MCP

What it does

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

#tdd#testing#red-green-refactor#unit-tests#debugging#best-practices

Quality judgment

completeness

9.0/10

clarity

9.0/10

trigger quality

8.0/10

examples

9.0/10

structure

9.0/10

overall

9.0/10

An exceptionally thorough and well-structured TDD skill with concrete good/bad examples, a full worked bug-fix walkthrough, rationalization counterarguments, red flags, and verification checklists. Trigger description is clear and appropriately broad; only minor gaps are lack of guidance for non-JS/TS stacks and edge cases like async/flaky tests.

Files (3)

LICENSE · 1.0 KBSKILL.md · 9.4 KBwriting-good-tests.md · 8.1 KB