QA review and test planning
Assign a feature, release, or PR and the QA reviewer builds a risk-based test plan, exploratory charters, edge-case matrix, and coverage-gap report for approval.
Saves you ~1.5 h / run
How it works
- Trigger
- When you start the “QA plan delivery” workflow.
- Job
- Build and verify a risk-based QA and test plan.
- Outcome
- A verified, risk-based QA and test plan.
What it installs
Agents 2
-
QA Reviewer
Reads specs, releases, or PRs; maps scenarios and risks; and drafts QA plans, exploratory charters, and automation recommendations.
-
QA review and test planning Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
QA review and test planning quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
QA plan delivery
Build and independently verify a risk-based QA plan before human approval.
Goals 1
-
QA risks visible before release
Keep release and feature risks explicit before implementation or launch. Success looks like: Every assigned change has a risk-based test plan, edge-case matrix, coverage-gap report, and explicit open questions before humans approve the release path.
Skills 2
-
qa-test-planner
Risk-based QA planning for requirements, acceptance criteria, test matrices, exploratory charters, release risks, and coverage gaps. Adapted from softaworks/agent-toolkit/qa-test-planner.
-
breakdown-test
Break requirements into testable scenarios and acceptance cases, separating setup, action, expected result, and edge cases. Adapted from github/awesome-copilot/breakdown-test.
Requirements
- Feature spec, release notes, or pull request — Needs the product change to review: a spec, acceptance criteria, release scope, PR diff, or linked issue set.
- Connected repository optional — A repository lets the agent inspect existing tests and code paths; without it, the bundle still produces a plan from the supplied spec and documents.
Setup guide
How to Plan QA Tests With an Agent
Turn a feature, release, or PR into a risk-based QA plan with scenarios, charters, coverage gaps, and approval.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.