Individual skill

regression-test-plan

Design and prioritize a regression test suite so changes don't break what worked. Use when asked to plan regression testing, build a regression suite, decide what to re-test after a change, or trim a bloated regression pack. Produces a risk-based regression plan — what to re-test and why, prioritised tiers (smoke → full), automation candidates, and a run strategy per release — so coverage matches risk and the suite stays fast.

plugins/pm-qa/skills/regression-test-plan/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Regression Test Plan Skill

Regression testing protects what already works — but re-running everything every time is slow and wasteful, and
testing too little ships breakage. The answer is **risk-based**: re-test what changed, what it touches, and what
hurts most if it breaks. This skill builds that prioritised plan and a run strategy, so coverage tracks risk and
the suite doesn't balloon.

## Working from a brief

Given "we're shipping a checkout change, what should we regression-test?", **produce the plan anyway** — infer
the impacted areas and a sensible prioritisation, labelling assumptions. Tie scope to change-impact and risk.
Never hand back a question instead of a plan.

## Required Inputs
Back to top