Route PWDEV QA work
Select one installed qa-* workflow without expanding the user's authority. The router does
not perform the selected workflow itself.
Read workflow, safety, and
artifacts before routing.
Inputs
- The user's explicit objective and requested operation.
- Existing project context, requirements, criteria, approvals, target, and constraints.
- The observed testing surface and risk when the explicit objective does not identify a
workflow.
- The QA skills actually present in the active plugin installation.
Procedure
- Identify the explicit intent first. Do not reinterpret
review, status, or another named
workflow from the tools that happen to be available.
- If explicit intent is absent, use the observed surface to narrow the choice, then use risk to
choose the smallest workflow that answers the objective. Never infer authorization from risk.
- Select the candidate from this routing table:
| Intent |
Candidate |
| initialize |
qa-init |
| strategy |
qa-strategy |
| execute tests |
qa-test |
| explore |
qa-explore |
| regression |
qa-regression |
| bug |
qa-bug |
| review |
qa-review |
| release |
qa-release |
| report |
qa-report |
| status |
qa-status |
| tooling |
qa-tooling |
- Validate the selected route before returning it: the plugin-relative path
skills/<candidate>/SKILL.md must exist and be a regular file. A missing, non-regular, or
unreadable target is an error; never claim that an unavailable skill ran.
- State why the selected candidate applies. Identify close alternatives as not applicable and
explain why. If no installed candidate fits, stop with an explicit routing error.
- Preserve external requirements, criteria, states, and approvals. The selected workflow may
consume them but cannot silently replace their authority.
- Hand off to exactly one selected workflow and apply its authorization and stop conditions.
Output
Return this compact routing record before entering the selected skill:
ROUTE: <installed qa-* skill>
WHY: <explicit intent, or observed surface and risk>
NOT_APPLICABLE: <nearby candidates and reasons, or none>
LIMITATIONS: <missing context or tools, or none>
NEXT: <selected workflow entry>
If criteria required by the selected workflow are absent, do not invent them. Record the
limitation and let the common workflow contract produce BLOCKED.
Failure modes
- No explicit intent and insufficient surface or risk context: ask one focused question.
- Selected skill path is absent, unreadable, a directory, or a symlink: return a routing error.
- Required criteria are absent: preserve the absence; the QA result is
BLOCKED, never PASS.
- A requested operation exceeds authorization: stop before execution and identify the exact
authorization needed.
- A tool is missing or unverified: report the limitation; never fabricate an execution.
Safety
- Routing never authorizes load, penetration testing, production access, or external effects.
qa-review and qa-status remain read-only even if the project has writable tools.
- Never install tools, change personal configuration, publish, push, merge, or correct product
code automatically.
- Follow the evidence boundary and sanitization requirements before any artifact is accepted.
Related skills
The workflow candidates are the installed qa-* skills in the table above. qa-tooling is the
tool recommendation entry. Specialist guidance uses installed qa-specialist-* skills only
after a workflow requests the relevant surface; absence is a limitation, not an invented route.
1---2name: qa3description: Use when a user asks for QA planning, execution, review, release assessment, reporting, status, or test-tool recommendations and the correct PWDEV QA workflow must be selected safely.4metadata:5 source: https://skillmd.com/skills/pwdev-solucoes/qa6---78# Route PWDEV QA work910Select one installed `qa-*` workflow without expanding the user's authority. The router does11not perform the selected workflow itself.1213Read [workflow](../../references/workflow.md), [safety](../../references/safety.md), and14[artifacts](../../references/artifacts.md) before routing.1516## Inputs1718- The user's explicit objective and requested operation.19- Existing project context, requirements, criteria, approvals, target, and constraints.20- The observed testing surface and risk when the explicit objective does not identify a21 workflow.22- The QA skills actually present in the active plugin installation.2324## Procedure25261. Identify the explicit intent first. Do not reinterpret `review`, `status`, or another named27 workflow from the tools that happen to be available.282. If explicit intent is absent, use the observed surface to narrow the choice, then use risk to29 choose the smallest workflow that answers the objective. Never infer authorization from risk.303. Select the candidate from this routing table:3132| Intent | Candidate |33|---|---|34| initialize | `qa-init` |35| strategy | `qa-strategy` |36| execute tests | `qa-test` |37| explore | `qa-explore` |38| regression | `qa-regression` |39| bug | `qa-bug` |40| review | `qa-review` |41| release | `qa-release` |42| report | `qa-report` |43| status | `qa-status` |44| tooling | `qa-tooling` |45464. Validate the selected route before returning it: the plugin-relative path47 `skills/<candidate>/SKILL.md` must exist and be a regular file. A missing, non-regular, or48 unreadable target is an error; never claim that an unavailable skill ran.495. State why the selected candidate applies. Identify close alternatives as not applicable and50 explain why. If no installed candidate fits, stop with an explicit routing error.516. Preserve external requirements, criteria, states, and approvals. The selected workflow may52 consume them but cannot silently replace their authority.537. Hand off to exactly one selected workflow and apply its authorization and stop conditions.5455## Output5657Return this compact routing record before entering the selected skill:5859```text60ROUTE: <installed qa-* skill>61WHY: <explicit intent, or observed surface and risk>62NOT_APPLICABLE: <nearby candidates and reasons, or none>63LIMITATIONS: <missing context or tools, or none>64NEXT: <selected workflow entry>65```6667If criteria required by the selected workflow are absent, do not invent them. Record the68limitation and let the common workflow contract produce `BLOCKED`.6970## Failure modes7172- No explicit intent and insufficient surface or risk context: ask one focused question.73- Selected skill path is absent, unreadable, a directory, or a symlink: return a routing error.74- Required criteria are absent: preserve the absence; the QA result is `BLOCKED`, never `PASS`.75- A requested operation exceeds authorization: stop before execution and identify the exact76 authorization needed.77- A tool is missing or unverified: report the limitation; never fabricate an execution.7879## Safety8081- Routing never authorizes load, penetration testing, production access, or external effects.82- `qa-review` and `qa-status` remain read-only even if the project has writable tools.83- Never install tools, change personal configuration, publish, push, merge, or correct product84 code automatically.85- Follow the evidence boundary and sanitization requirements before any artifact is accepted.8687## Related skills8889The workflow candidates are the installed `qa-*` skills in the table above. `qa-tooling` is the90tool recommendation entry. Specialist guidance uses installed `qa-specialist-*` skills only91after a workflow requests the relevant surface; absence is a limitation, not an invented route.