• You receive a vague request like "help me test this" and must pick the right testing approach quickly.
• A PM or developer asks which QA skill should be used first under tight time.
• A new QA member needs a routing guide from problem type to executable skill.

• Identify the best-fit next skill for the current problem and context.
• Produce a clear decision path (why this skill, why now, what next).
• Reduce trial-and-error and avoid starting with the wrong testing method.

1. Classify request type: requirement quality, feature correctness, API, performance, security, release risk, or reporting.
2. Extract constraints: deadline, environment, data availability, automation maturity, and business criticality.
3. Match constraints to candidate skills and rank by impact vs. effort.
4. Pick one primary skill and one fallback skill with trigger conditions.
5. Define expected output from selected skill before execution.
6. Re-route only when evidence shows mismatch.

Input:

• "Login API changed, release in 2 days, no regression report yet."

Output:

• First: api-testing for contract and regression scope
• Second: test-reporting for release-readiness evidence
• Reason: highest risk is integration break before release

Input:

• "Checkout flow fails intermittently on mobile"

Output (problem):

• Route directly to test-case-writing without reproducing failure context
• Misses mobile-testing as the first diagnostic step

• Do not replace deep execution skills; this skill is for routing and prioritization.
• Do not provide random skill lists without decision logic.
• Do not ignore business priority and release window.
• Do not lock to one route when new evidence conflicts.
• Do not claim final quality status without downstream execution evidence.