Scrum🔴 scrumia-tdd
One named point of the implementation contract: how we test.
slot · none version · 0.5.0
What it is responsible for
Refines a single question the implementation module leaves open — the red-green-refactor cycle operationalised for an agent, where the mock boundary sits, which of the three levels — unit, integration, end-to-end — an invariant belongs to, and how an acceptance criterion maps to a test that can actually fail at the lowest level where it could.
What it refuses
It does not own the stack, the file structure or the design principles — and where it disagrees with the implementation module, the implementation module wins. It carries no test command of its own, and sets no coverage threshold: the per-level commands are the project's, and the coverage union is a map of what no level reaches, never a gate.
The assumption it makes
Assumes a failing test is the cheapest specification you can write. Costs a slower first pass, paid back only if the code outlives the sprint that produced it.
Its skills
scrumia-tddscrumia-tdd-auditscrumia-tdd-refactor
What it plugs into
| Register | Direction | Module |
|---|---|---|
audit | contributes | scrumia-github-project |
implement | contributes | scrumia-github-project |
review | contributes | scrumia-github-project |
Install it
/plugin install scrumia-tdd@scrumia