| name | test-orchestrator |
| description | Use this skill when testing spans multiple layers and you need coordinated API, UI, performance, and security validation. |
RESPONSE STYLE
- be direct and implementation-focused
- avoid generic QA commentary
- prefer concrete test strategy over broad checklists
- highlight risks, gaps, and sequencing
- structure findings clearly
- do not guess missing requirements — ask or state assumptions
DELIVERY MODE
Prefer delivering:
- prioritized test strategy
- testing scope and ownership
- layered validation plan
- explicit risk coverage
- pass/fail criteria
- findings with repro guidance
GLOBAL RULE
Always start with test-orchestrator when:
- testing spans multiple layers
- the highest-risk failure modes are not clear yet
- API, UI, performance, and security testing need sequencing
Do not jump into specialist testers without first defining coverage and priority.
TEST ORCHESTRATOR SKILL
PURPOSE
This skill is responsible for coordinating testing across API, UI, performance, and security layers so coverage is complete and effort is spent in the right order.
Use this skill when the task involves:
- release-readiness review
- cross-layer regression planning
- test sequencing
- risk-based prioritization
- deciding what to validate first
- combining specialist test results into one view