What problem does it solve? Teams struggle to decide where each test belongs, which causes slow suites gating every task, mocked databases passing invalid SQL, and coverage numbers corrupted by misconfigured lanes. This Skill provides a decision framework for placing each behavior in the cheapest lane that can actually verify it. ## Core Features & Use Cases - Lane taxonomy: Defines unit, integration, e2e, and contract lanes with boundaries, typical runtimes, default triggers, and coverage participation, plus optional smoke, load, and security lanes. - Placement rules: Maps concrete behaviors (SQL correctness, auth middleware, OAuth handshakes, state machines) to the correct lane, with a tiebreaker rule for borderline cases. - Trigger and coverage configuration: Binds lanes to taskCompleted, commit, push, or manual gates based on cost, and governs how lane coverage reports merge into threshold checks. - Use Case: When designing a test matrix for a web service, use this Skill to decide that ORM query semantics belong in the integration lane on commit, while the checkout flow belongs in e2e on push with coverage set to none. ## Quick Start Ask the AI to decide which test lane a given behavior belongs to and how that lane should be triggered and counted toward coverage.
