Two testing skills · both proven

tdd vs test-driven-development

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work.

tdd

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Category: Testing
Source: mattpocock/skills
License: MIT
Proof model: claude-opus-5-5
Brief: “Implement a function that parses a cron expression (the standard five fields) and returns the next run time after a given date, in TypeScript. Present the work as a single HTML page with two columns: the test file on the left and the implementation on the right, each in a code block, with a short note at the top on the order you did things in and anything you decided not to support.”
Skill commit: 5beb35b

Without the skillWith tdd

⇆

Without, runWith tdd, run3 independent runs per side, none selected by hand.

Download the with-skill page

test-driven-development

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

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “Implement a function that parses a cron expression (the standard five fields) and returns the next run time after a given date, in TypeScript. Present the work as a single HTML page with two columns: the test file on the left and the implementation on the right, each in a code block, with a short note at the top on the order you did things in and anything you decided not to support.”
Skill commit: bb92a77

Without the skillWith test-driven-development

⇆

Without, runWith test-driven-development, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to tdd or alternatives to test-driven-development.