skills.rest
Takkuya
TakkuyaCOMMUNITY
Explore all skills by this author →
GitHub

qa-test-plan

Generates lean HTML manual test plans from PRs, Notion tasks, or pasted deliverables.

Updated Jul 7, 2026
Search Tags:#pull request#edge cases#qa#manual testing#notion#test plan#html report
One-click install
npx skills add https://github.com/Takkuya/claude-skills --skill qa-test-plan-takkuya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-test-plan
Source: https://github.com/Takkuya/claude-skills/tree/main/qa-test-plan
Command: npx skills add https://github.com/Takkuya/claude-skills --skill qa-test-plan-takkuya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing QA test plans from scratch is slow and often produces bloated checklists nobody reads. This Skill turns a pull request, Notion task, or pasted deliverable description into a short, actionable manual test plan in HTML that a QA engineer can read end-to-end before testing. ## Core Features & Use Cases - Multi-source context gathering: Accepts GitHub or Azure DevOps PR URLs (including multiple PRs treated as one delivery), Notion pages (tasks, bugs, roadmap items), or plain pasted text, and cross-references them. - Code-aware scenario discovery: Inspects the diff, greps for callers and consumers of changed symbols, and identifies adjacent flows, feature flags, and edge cases grounded in the actual code. - Structured lean HTML output: Produces a self-contained HTML plan with summary, prerequisites, quick setup, golden path, fallback flows, and P1/P2-prioritized edge cases, with an optional --verbose mode for platform matrices and acceptance criteria. - Use Case: Paste a GitHub PR URL plus its linked Notion task and receive a single consolidated HTML test plan covering the golden path, fallback behavior, and targeted edge cases for the QA team. ## Quick Start Ask the assistant to generate a QA test plan from your pull request URL, for example by saying: generate a QA test plan for https://github.com/myorg/myrepo/pull/1234.

Frequently Asked Questions about qa-test-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a QA test plan from a GitHub pull request?▼

Pass the pull request URL to the skill and it fetches the PR metadata, checks out the branch, inspects the diff, and produces an HTML test plan with golden path, fallback, and edge case scenarios. Multiple PR URLs are consolidated into a single end-to-end plan.

How to create a manual test plan from a Notion task?▼

Provide the Notion page URL and the skill fetches the full page, reads its properties, and builds a test plan from the product context. Multiple Notion URLs are supported, with roadmap pages driving expected behavior and dev tasks defining technical scope.

Does this skill support Azure DevOps pull requests?▼

Yes, it detects the platform from the URL and supports both GitHub and Azure DevOps pull request links. It reuses existing PR analysis recipes to collect title, body, changed files, and diffs from either platform.

Can this skill write automated E2E tests instead of a manual plan?▼

No, this skill is strictly for manual test plans written in natural language for human QA testers. For automated E2E tests you should use a dedicated E2E skill, and for code review use a review-focused skill instead.

What inputs does the QA test plan generator accept?▼

It accepts GitHub or Azure DevOps PR URLs, Notion page URLs, or pasted text describing the deliverable, and combinations of all three. More context produces a better plan, and pasted text alone yields a shallower plan since no code is inspected.

When should I use the verbose mode for a test plan?▼

Use the --verbose flag when the QA team is less experienced or the delivery is too large for the lean format. It adds platform matrices, acceptance criteria checklists, plausible regressions, open questions, known bugs, and a bug report template.

Related Skills

Explore More Software Engineering Skills→
JocysComJocysCom
206

pr-review

Automate Azure DevOps pull request reviews with Python scripts.

Official
Advanced
Euraika-LabsEuraika-Labs
14

team-qa

Orchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.

Official
Advanced
jordanhubbardjordanhubbard
105

qa-engineer

Validate APIs, services, and UI workflows through manual and automated testing.

Community
Advanced
unbakedcosmosunbakedcosmos

bmad-qa-generate-e2e-tests

Generates API and end-to-end automated tests for existing project features.

Community
Intermediate