Review Rfc
nurettincoban/ai-prd-workflow
Review an implemented RFC in a fresh context against its acceptance criteria, RULES.md and the test plan, and save the review to reviews/.
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.
Install QA Handoff Package
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-package --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qa-handoff-package .claude/skills/qa-handoff-package && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .claude/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-packageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-package --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qa-handoff-package .agents/skills/qa-handoff-package && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .agents/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-package --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qa-handoff-package .cursor/skills/qa-handoff-package && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .cursor/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/qa-handoff-package--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-package --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qa-handoff-package .gemini/skills/qa-handoff-package && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .gemini/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-packageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qa-handoff-package .github/skills/qa-handoff-package && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .github/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills qa-handoff-package --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qa-handoff-package .opencode/skills/qa-handoff-package && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qa-handoff-package" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/qa-handoff-package into .opencode/skills/qa-handoff-package/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-handoff-package", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qa-handoff-package- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 542 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 6 steps: Cover every AC. Each acceptance… → The happy path is the easy 30%. The… → Reproducibility is setup. Name the exact… → …
- Asked to prep a QA handoff
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: A Handoff QA Can Run and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
QA Handoff Package is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories and Test generation. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to prep a QA handoff
- What should QA test here
- Write test scenarios for this story
- Make this ready for QA
Example prompts
- “ready for QA”
- “/qa-handoff-package”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Cover every AC. Each acceptance criterion gets a concrete scenario — no AC left unverified.
- The happy path is the easy 30%. The value is the edge and negative cases: empty, max, invalid, unauthorised, offline, concurrent…
- Reproducibility is setup. Name the exact data, accounts, roles, and flags — "test it" without setup wastes QA's morning.
- Point at the risk. Where the diff touches shared code or a fragile area, call it out — including regressions in neighbouring features.
- Bound it. State what's out of scope so QA doesn't test the whole app for a small change.
- Ground in the actual change. Scenarios match what was built, not what the story wished for.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
QA Handoff Package loads about 1.1k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 542 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 542 words, ~1,065 tokens.
Download SKILL.mdSave it as
.claude/skills/qa-handoff-package/SKILL.md (or your agent's skills folder).- name
- qa-handoff-package
- description
- 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.
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 reality
- Environments & data — where QA tests, and what setup/flags/accounts are needed
- Known risk/complexity — anything the dev is worried about, or areas the change touches indirectly
Framework: A Handoff QA Can Run
- Cover every AC. Each acceptance criterion gets a concrete scenario — no AC left unverified.
- The happy path is the easy 30%. The value is the edge and negative cases: empty, max, invalid, unauthorised, offline, concurrent, mid-migration.
- Reproducibility is setup. Name the exact data, accounts, roles, and flags — "test it" without setup wastes QA's morning.
- Point at the risk. Where the diff touches shared code or a fragile area, call it out — including regressions in neighbouring features.
- Bound it. State what's out of scope so QA doesn't test the whole app for a small change.
- Ground in the actual change. Scenarios match what was built, not what the story wished for.
Show full SKILL.md (206 more words)Show less
Output Format
QA Handoff — [story] · build: [MR/PR ref]
Scenarios (by acceptance criterion)
| AC | Scenario | Expected |
|---|
Edge & negative cases
- [empty / boundary / invalid / permission / concurrency / offline …]
Setup to reproduce
- Environment: … · Accounts/roles: … · Feature flags: … · Seed data: …
Risk areas / possible regressions
- [where this change might have broken something nearby].
Out of scope
- [what not to test for this change].
Quality Checks
- Every acceptance criterion has at least one scenario
- Edge and negative cases are included, not just the happy path
- Exact data/environment/flag setup is specified for reproducibility
- Risk areas and possible regressions are called out
- An explicit out-of-scope list bounds the testing
- Scenarios reflect what was actually built, not just the story text
Anti-Patterns
- Happy-path only — the bugs live in the edges.
- "Just test the story" with no data/environment setup — a lost QA morning.
- No scope boundary — QA re-tests the whole app for a one-line change.
- Ignoring regressions in features the change touches indirectly.
- Scenarios from the story, not the build — testing what was wished, not what shipped.
Example Trigger Phrases
- "Prep a QA handoff for this story and its MR."
- "What should QA test here, including edge cases and setup?"
- "Write test scenarios mapped to these acceptance criteria."
- "Make this ready for QA — what's in and out of scope?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/qa-handoff-package of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
QA Handoff Package next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| QA Handoff Package this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Review Rfcnurettincoban/ai-prd-workflow | 298 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Test Scenariosphuryn/pm-skills | 27k | — | ~866 | Automated safety check: Pass | MIT | |
| Test Authorjpicklyk/task-orchestrator | 207 | — | ~8.2k | Automated safety check: Pass | MIT | |
| Dispatching To Codexccplugins/awesome-claude-code-plugins | 970 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Argent QA Flowsbbplayer-app/BBPlayer | 1.2k | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Test Scenarios
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
Test Author
jpicklyk/task-orchestrator
Test authoring framework for items carrying the needs-test-author trait.
Dispatching To Codex
ccplugins/awesome-claude-code-plugins
A skill your agent uses when the user explicitly asks to hand a task to Codex — "use codex", "delegate this", "send it to codex", "交给codex", "派给codex", or the /delegate command.
Argent QA Flows
bbplayer-app/BBPlayer
Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria.
AI Test Generation
petrkindlmann/qa-skills
Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about QA Handoff Package
What does QA Handoff Package 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. QA Handoff Package is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use QA Handoff Package?
QA Handoff Package fits situations like: asked to prep a QA handoff; what should QA test here; write test scenarios for this story; make this ready for QA.
How do I install QA Handoff Package in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a claude-code`. Or copy the skill folder (skills/qa-handoff-package in mohitagw15856/pm-claude-skills) into .claude/skills/qa-handoff-package in your project. Claude Code loads it when a task matches its description.
How do I install QA Handoff Package in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a codex`. Or copy the skill folder (skills/qa-handoff-package in mohitagw15856/pm-claude-skills) into .agents/skills/qa-handoff-package in your project. Codex loads it when a task matches its description.
Can I use QA Handoff Package in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill qa-handoff-package -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-handoff-package, .gemini/skills/qa-handoff-package, .github/skills/qa-handoff-package and .opencode/skills/qa-handoff-package in your project.
What does QA Handoff Package need to run?
SKILL.md names no scripts, command-line tools or credentials: QA Handoff Package is instructions for the agent only.
Does QA Handoff Package access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is QA Handoff Package safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does QA Handoff Package use?
QA Handoff Package is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does QA Handoff Package use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to QA Handoff Package?
Skills that share tags, products or a category with QA Handoff Package: Review Rfc (nurettincoban/ai-prd-workflow, 298 stars), Test Scenarios (phuryn/pm-skills, 27k stars), Test Author (jpicklyk/task-orchestrator, 207 stars) and Dispatching To Codex (ccplugins/awesome-claude-code-plugins, 970 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains QA Handoff Package?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.