What problem does it solve?
It eliminates the gap between written specs and executable test suites by converting spec-defined behaviors into real, language-conventional test files while ensuring the implementation cannot cheat with no-op stubs.
Core Features & Use Cases
- Spec-to-test generation: Converts every Section 5
TEST: ... block from a spec bead into runnable tests with setup, execution, assertions, and rationales.
- Contract strengthening: Adds at least five additional edge/error tests beyond the spec to cover boundary conditions, invalid inputs, concurrency, and persistence-related scenarios.
- Delegation verification: For delegating/adapter patterns, writes delegation-assertion tests that spy on real dependencies and fail if the implementation doesn’t actually call them.
- Path convention compliance: Places test files according to the project’s
CLAUDE.md convention (or sensible language defaults) and uses one test file per module when specs cover multiple modules.
- Strict safety on outputs: Ensures test agents write only test files and never create or modify implementation source files.
Quick Start
Generate tests for the spec bead id 'bd-1234' by creating only the conventional test files required by the project’s testing framework.