What problem does it solve? Deciding what to test, at which level, and in what order is a recurring source of wasted effort: tests that never fail prove nothing, and coverage spent at the wrong pyramid level costs maintenance without catching defects. This Skill provides a disciplined test-first method for planning and writing tests. ## Core Features & Use Cases - Red-Green-Refactor Discipline: Enforces writing a failing test first, confirming it fails for the right reason, then implementing the minimal code to pass before refactoring. - Test Pyramid Guidance: Allocates tests across unit, integration, and end-to-end levels as a cost gradient, pushing tests down to the cheapest level that catches the same defect. - Coverage Planning: Produces a test plan naming what to cover (business-critical paths, error handling, edge cases, security boundaries, data integrity), what to skip, and explicit gaps in existing coverage. - Use Case: When starting a new feature, ask for a test-first plan and receive a behavior-by-behavior sequence of tests with the pyramid level for each, plus example cases. ## Quick Start Ask the assistant to plan a test-first strategy for the feature you are about to build, including pyramid levels and coverage gaps.
