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.
npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 Ask for these only if they aren't already provided (else infer and label): - **The change** — what's being released/modified, and what it touches (and integrates with). - **Critical paths** — the flows that must never break (revenue, auth, data integrity). - **Existing coverage** — current regression cases/automation, if any, and how long a full run takes. - **Constraints** — time/resources per release, and manual vs. automated capacity. ## Output Format ### Regression Plan: [release/change]
- Working from a brief
- Required Inputs
- Output Format
- Regression Plan: [release/change]
- Quality Checks
- Anti-Patterns
- Based On
What does the regression-test-plan skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill regression-test-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.