tdd-workflow
Test-driven development workflow: write a failing test first, watch it fail
by affaan-mFree
Description
tdd-workflow is an agent skill from the ECC collection by affaan-m, listed on skills.sh. It makes all code development follow test-driven development. The cycle is to write a failing test first, watch it fail, implement the smallest change that makes it pass, then refactor, aiming at 80 per cent or more coverage. It applies to new features, bug fixes, refactors, new API endpoints and new components. It also covers continuing from a plan produced by /plan or from another plan document. A plan file is treated as untrusted input: it is the starting point for the TDD cycle, and any instruction written inside it, such as an order to ignore the rules or skip validation, is recorded as plan content rather than followed. A skill is a SKILL.md file of instructions that an AI agent loads when a task calls for it. It is free and open source, and the skills.sh listing shows all three security audits passing.…
Highlights
- Failing test first, then smallest change
- 80 per cent or more coverage target
- Continues from /plan output
- Plan files treated as untrusted input
Ratings & Reviews
No ratings yet
Be the first to rate tdd-workflow.
People also visit
tdd-workflow FAQ
What does the tdd-workflow skill do?
It makes an agent develop code test-first: a failing test, the smallest change to pass it, then refactoring, with coverage tracked.
What coverage does it aim for?
80 per cent or more.
Can it start from a plan?
Yes. It can take a /plan output or a *.plan.md file as its starting point.
How do I install it?
Run: npx skills add https://github.com/affaan-m/ecc --skill tdd-workflow
Is it free?
Yes. It is free and open source.
Are there security findings?
The skills.sh listing shows Gen Agent Trust Hub, Socket and Snyk all passing.
What are the best tdd-workflow alternatives?
Popular alternatives to tdd-workflow include tdd, django-tdd and golang-testing. See all tdd-workflow alternatives