QA Skill Router
The user asks what to test, which testing approach or skill to use, "where do I start", or describes a QA task without naming a skill — routes the request to the right software-testing skills and gives the order to apply them.
Pick the smallest set of skills (usually 1–3) that fits the task, load them, and say which you chose and why. Do not load skills that do not apply.
Step 1 — Classify the request
Ask (or infer): What is the artifact (code, API, UI, data, infra, model)? What is the goal (find bugs, prevent regressions, prove compliance, measure quality)? What is the risk? If the artifact or goal is unclear and guessing would waste effort, ask one short question.
Step 2 — Route by intent
Step 3 — Sequence
Typical order for a new feature: requirements-testing-review → test-design-techniques → unit-testing/tdd-workflow → api-testing or integration-testing → e2e-testing (few, critical) → non-functional (performance-testing, accessibility-testing, security) → release-readiness-testing → production-monitoring-synthetic-testing.
Step 4 — Respond
State the chosen skills in one line each ("api-testing — you have a REST API with auth"), then proceed with the work. Offer the matching slash command when the tool supports commands (/test-plan, /unit-tests, /api-tests, /e2e-tests, /security-audit, /perf-plan, /a11y-audit, /flaky-triage, /release-check, /qa-audit).
Safety
Security and load testing only against systems the user owns or is explicitly authorized to test; prefer staging; never use real customer data or live payment credentials.