qa-handoff-package
Turn a story and its change into a clean 'ready for QA' package — test scenarios, edge cases, the data and environment setup, and what's explicitly out of scope. Use when asked to prep a QA handoff, what should QA test here, write test scenarios for this story, or make this ready for QA. Produces the scenarios mapped to acceptance criteria, the edge/negative cases devs forget, the exact data and environment setup to reproduce, the risk areas to probe, and the out-of-scope list so QA doesn't chase the wrong things.
npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package --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.
# QA Handoff Package The "ready for QA" that isn't — a story tossed over the wall with no test data, no edge cases, and no idea what changed — is how bugs slip and QA burns a day setting up. This turns the story and its change into a real handoff: scenarios tied to the acceptance criteria, the negative and edge cases developers reliably forget, the exact data/environment to reproduce, and a clear line around what's *not* in scope, so testing is focused, not archaeology. ## What This Skill Produces - **Test scenarios mapped to acceptance criteria** — every AC has at least one way to verify it - **Edge & negative cases** — empty/boundary/invalid inputs, permissions, concurrency, the forgotten paths - **Data & environment setup** — the exact accounts, feature flags, seed data, and env needed to reproduce - **Risk areas to probe** — where this change is most likely to have broken something (incl. nearby regressions) - **Out of scope** — what QA should *not* spend time on for this change ## Required Inputs Ask for these if not provided: - **The story & acceptance criteria** — what it's meant to do - **The change** — what was built (a summary or the MR/PR diff), so scenarios match realit
- What This Skill Produces
- Required Inputs
- Framework: A Handoff QA Can Run
- Output Format
- QA Handoff — [story] · build: [MR/PR ref]
- Scenarios (by acceptance criterion)
- Edge & negative cases
- Setup to reproduce
- Risk areas / possible regressions
- Out of scope
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the qa-handoff-package skill do?
Turn a story and its change into a clean 'ready for QA' package — test scenarios, edge cases, the data and environment setup, and what's explicitly out of scope. Use when asked to prep a QA handoff, what should QA test here, write test scenarios for this story, or make this ready for QA. Produces the scenarios mapped to acceptance criteria, the edge/negative cases devs forget, the exact data and environment setup to reproduce, the risk areas to probe, and the out-of-scope list so QA doesn't chase the wrong things.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package --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.