What problem does it solve? Teams often write tests ad hoc, missing edge cases and producing brittle or flaky suites. This Skill acts as a router for test design: it exhaustively extracts the behaviors worth testing from a feature, module, API, or PR diff, assigns concrete test methods to each, and bridges the results into implementation and regression. ## Core Features & Use Cases - Behavior Extraction (test-extract): Enumerates all testable behaviors into a numbered T-ID ledger, and for reviews reads existing tests bidirectionally against the ledger. - Method Selection (test-catalog): Assigns each behavior a technique from a catalog of 40 test methods (equivalence partitioning, state transition, mutation testing, property-based testing, and more), opening only the relevant reference. - Verification & Handoff (test-verify): Bridges to TDD implementers, enforces execution gates (coverage back-tracing, flaky checks, mutation), and fixes tests into CI as regression. - Use Case: Before planning a new API endpoint, run the pipeline to produce a complete T-ID ledger with assigned methods, then hand it to the implementer so every failing test traces back to a designed behavior. ## Quick Start Ask the assistant to design the test cases for a specific feature, module, or PR diff you are working on.