qa-process
Test process and strategy: risk-based testing, test strategies, Definition of Done, smoke gates, test pyramid balance, effort estimates and post-mortems. Also covers E2E suite budgets, test ideas from stories and live features, framework choice, and attack-surface checklists. Agents (release-readiness-checker, quality-coach, release-engineer) run multi-gate go / no-go checks, audit work against the Definition of Done, and walk a release runbook with human gates.
/plugin install qa-process@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Foundations
- Version
v1.12.10- Contents
- 12 skills · 3 agents
Skills12
attack-surface-test-checklistUse when a pull request, release branch or feature is about to be security tested and needs a targeted test list.skilldefinition-of-doneUse when a team has no Definition of Done, wants to revise it, or is about to mark a story or PR done without checking it.skille2e-suite-budgetUse when CI is slow or dominated by end-to-end tests, flaky failures are rising, or for a quarterly suite review.skillframework-choice-advisorUse when picking a test automation framework or QA tool before adopting it: Playwright vs Cypress vs Selenium, Appium vs Espresso/XCUITest, RestAssured vs Karate, k6 vs Locust.skillpost-mortem-authorUse after any user-visible incident to write a blameless post-mortem: a sourced timeline, root cause (what and why, not who), impact on users, revenue and SLOs, action items with owners, dates and success criteria, and what went well.skillrisk-matrixUse for any risk-based testing artifact: a risk matrix or register with likelihood x impact scores, a risk-storming session, calibrating ratings against real defects, or mapping each risk to the tests and monitors that cover it.skillsmoke-suite-gateUse when a team needs a fast per-deploy gate: a smoke suite of 5-15 critical journeys (login, checkout, payment, main read path) that runs in under 5 minutes as E2E or API tests and blocks the deploy when it fails, with retries for transient failures.skilltest-case-from-live-featureUse when a feature has no story, acceptance criteria or docs, only a running app, recording, screenshot or verbal brief, and it needs test cases.skilltest-case-ideation-from-storyUse when a thin or ambiguous user story or spec needs its test cases listed and agreed before automation.skilltest-effort-estimationUse when an epic or release is split into testable areas and someone must commit test capacity.skilltest-pyramid-balancerUse when asked about test distribution or balance: too many E2E tests, slow CI caused by tests, or rebalancing a suite.skilltest-strategy-authorUse when a project, release or feature needs a test strategy or master test plan that stakeholders sign off: scope, test types per layer, risk-based prioritization, tools, environments, exit criteria and ownership, plus a budgeted per-risk test plan with owners and effort.skill
Agents3
quality-coachAdversarial reviewer that critiques a story / PR / Increment against the team's Definition of Done - reads the team's docs/definition-of-done.md (or whichever path the project uses), then walks each DoD line and tags it met / not met / unverifiable, calling out which lines lack evidence in the PR.agentrelease-engineerBuilder/scaffolder agent that orchestrates the release runbook for one specific release - reads the team's docs/release-runbook.md (or the release-runbook-author template from qa-shift-right), executes its steps in order (smoke suite gate → canary deploy with metric thresholds → rollout / rollback decision), records pass/fail per step, and emits a release report.agentrelease-readiness-checkerOrchestrates a configurable multi-gate suite before a release and emits a single go / no-go verdict with per-gate evidence.agent
About qa-process
Test process + methodology - the risk-based testing umbrella (risk matrix + registers + storming + calibration + coverage mapping), Definition of Done authoring + adherence auditing, test strategy + risk-based test planning, blameless post-mortems, release readiness gates, smoke-suite gating, test-pyramid analysis, framework + vendor + tool selection, test effort estimation, E2E suite budgets, and test-case ideation from stories or live features.
Related reading
- Exploratory Testing Tours: Whittaker's Six Districts
- HTSM: Inside James Bach's Heuristic Test Strategy Model
- HICCUPPS-F: Nine Testing Oracles for Defending Your Bug Calls
- Session-Based Test Management (SBTM): Definition, Sessions and Metrics
- Precision in PROOF Debriefs: The Debriefer's 60-Second Test
- Exploratory Testing Charter: Template and Examples