test-driven-development
Enforces write-the-failing-test-first TDD before any implementation or bugfix code.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for test-driven-development, derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
A superpowers skill that mandates the red-green TDD loop: write the test, watch it fail, write minimal code to pass. Core principle is that an unwatched-fail test proves nothing. Instruction-only surface that dictates the order in which the agent writes tests versus implementation.
Key features and capabilities
- Test-first mandate
- Watch-it-fail verification
- Minimal-code-to-pass loop
Use cases
- Implementing a new feature test-first
- Writing a regression test for a bugfix