sumo-qa-implementing-with-tdd

What problem does it solve?

This Skill prevents “guessy” coding by forcing test-driven development discipline: you confirm what the test should catch, observe a real failing (red) test, and only then move toward green.

Core Features & Use Cases

• Risk-to-test alignment: Converts the named QA risk into a smallest failing test idea tied to the repo context.
• Strict red-phase guardrails: Ensures no production code is written before the failing test evidence exists, with narrow signature-only stubbing allowed.
• Technique-driven test design: Selects the appropriate test-design technique from the loaded catalogue (e.g., boundary-value analysis, decision tables) and uses it to craft a discriminator assertion.
• Run-and-show evidence: Captures the actual assertion failure (expected vs got) and uses that as the handoff basis.

Quick Start

Use sumo-qa-implementing-with-tdd when the approach has selected a TDD cycle (tdd-scaffold, regression-first, or coverage-first-then-refactor) and you want the assistant to walk red→green one confirmed step at a time.