What problem does it solve? Teams often write tests without clear agreement on scope, leading to missing coverage for critical logic or wasted effort on trivial CRUD code. This Skill enforces a structured decision process so tests are only written after the user confirms exactly which cases matter. ## Core Features & Use Cases - Test Scope Classification: Separates non-trivial business logic from CRUD-only behavior and identifies user-facing I/O surfaces that need end-to-end coverage. - User-Confirmed Test Cases: Requires an explicit, user-approved list of test cases, priorities, and constraints before any test is implemented. - Layered Coverage Rules: Maps approved cases to unit or end-to-end layers, with required performance checks for end-to-end flows, screenshot assertions for UI rendering, and migration tests when schema changes occur. - Use Case: When adding a new API endpoint, use this Skill to classify the change, propose candidate unit and end-to-end tests, confirm the exact cases with the requester, then implement and report coverage mapped back to the approved list. ## Quick Start Ask the assistant to plan the test coverage for your recent code change and confirm which specific test cases should be implemented.
