test-orchestrationlisted

## Routing Guidance **Priority Order:** Strategy precedes execution. Use STRATEGY when making decisions about tests. Use EXECUTE when writing or fixing tests. IF deciding what to test, coverage strategy, mocking approach, fixture design, or property-based testing → use STRATEGY IF writing tests first, running red-green-refactor, adding post-hoc coverage, or fixing failing tests → use EXECUTE IMMEDIATELY when the user says: 'fix tests', 'fix failing tests', 'tests are broken', 'restore test suite', 'update assertions' BEFORE implementing any new feature or bug fix when tests do not yet exist ## Decision Router | Mode | Trigger | Sub-modes | |------|---------|-----------| | STRATEGY | Deciding what to test, coverage, mocks, fixtures | COVERAGE, MOCK-STRATEGY, FIXTURE, PROPERTY-BASED | | EXECUTE | Writing tests, red-green-refactor, coverage addition | Test-Driven Development, Write Tests, Fix Tests | IF implementing a new feature from scratch → use Test-Driven Development (RED first) IF fixing a bug → use Test-Driven Development (write reproducing test first) IF adding test coverage for existing uncommitted changes → use Write Tests IF fixing failing tests after refactoring or dependency updates → use Fix Tests IF refactoring → tests must already exist and pass before starting --- ## §CONTRAST **DO NOT use this skill for:** - "Run the tests / see if they pass" — just run `cargo test` / `pytest` etc. directly; this skill is for *planning* and *fixing*, not for routine te