TDD feature builder
Hand the agent a spec and it turns each acceptance criterion into a failing test, watches it fail, writes the minimal code to pass, refactors green, and drafts a PR — features shipped test-first.
Saves you ~5.3 h / run
How it works
- Trigger
- When you start the “TDD feature” workflow.
- Job
- Plan the feature, write failing tests, implement and refactor green, verify the suite.
- Outcome
- A tested implementation and pull request draft.
What it installs
Agents 2
-
TDD Coding Agent
Turns each acceptance criterion into a failing test, implements minimally, refactors green, and drafts a pull request.
-
TDD feature builder Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
TDD feature builder quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
TDD feature
Plan the feature, write failing tests, implement and refactor green, verify the suite, then draft a PR for approval.
Goals 1
-
Features shipped test-first
Keep every feature arriving with behavioural tests that were written, and seen to fail, before the code. Success looks like: Each assigned spec ships with a behavioural failing-test-first suite covering every acceptance criterion and its edge cases, a green full suite, and an approved pull request — and no feature merges without test-first coverage.
Skills 3
-
test-driven-development
The red-green-refactor discipline: no production code without a failing test first, watch every test fail for the right reason, write minimal code to pass, then refactor green; behavioural tests over mocks. Adapted from obra/superpowers/test-driven-development.
-
writing-plans
Turn a spec into a bite-sized, testable implementation plan: scope-check, map the files, right-size tasks to a reviewer's gate, write single-action TDD steps with real content and no placeholders, then self-review against the spec. Adapted from obra/superpowers/writing-plans.
-
implement
Disciplined execution of a planned feature: TDD at the agreed seams, typecheck and single test files often, the full suite once at the end, frequent small commits, and a review before handing off. Adapted from mattpocock/skills/implement.
Requirements
- Connected repository — The agent reads the codebase and test suite, adds tests, implements the feature, and opens a pull request in your connected repository. Until repository access is connected, it works from the code supplied as attachments and drafts the PR for you to open.
Setup guide
How to Build Features With TDD
A practical guide to turning feature specs into failing tests, minimal code, green refactors, and reviewable PRs.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.