What problem does it solve? It prevents production behavior changes from being written without failing tests first, and stops teams from shipping code whose tests only appear adequate because coverage numbers look high. ## Core Features & Use Cases - RED-GREEN-REFACTOR workflow: Requires a failing behavior test before any production code, minimal implementation to pass, then assessed refactoring under a green safety net. - Fast feedback loop guidance: Directs use of repository-owned watch commands, Vitest changed/related selection, and affected one-shots instead of running the full suite after every edit. - End-of-phase mutation gate: Runs mutation testing once per PR-sized slice, or records explicit N/A with alternate evidence such as contract, integration, or operational proof. - Use Case: When adding a validation rule to a user service, write the failing behavior test first, implement the minimum code, keep the watcher green through refactors, then run the mutation gate before opening the PR. ## Quick Start Ask the agent to implement a new feature or bug fix using strict TDD with a failing test first and a mutation testing check before the PR.