What problem does it solve? Teams often chase coverage percentages while their tests assert nothing meaningful, leaving business logic paths untested and boundary drift discovered only in production. This Skill turns a requirement's business rules into a concrete, layered test strategy so coverage guarantees behavior rather than a number. ## Core Features & Use Cases - Layered Test-Level Plan: Decides what to test at unit, integration, contract, e2e, and regression levels, with an owner assigned to each. - Business-Logic-to-Scenario Mapping: Converts every business rule into happy-path, failure-path, and boundary scenarios, plus edge-case parameters like null, max, duplicate, and overflow. - Contract-Test Boundaries: Identifies consumer-driven contract points (e.g., Pact for service/REST boundaries, tool-schema governance for agent boundaries) between unit and e2e levels. - Use Case: Given a wallet top-up feature, the Skill produces a strategy covering ledger math unit tests, a consumer-driven Pact contract for the provider callback, one e2e happy-path journey, and edge cases like duplicate callbacks and zero amounts. ## Quick Start Ask the agent to turn this feature's business logic into a layered test strategy with scenario mapping and contract-test boundaries.
