Qa Test Planner
CheckedGenerates comprehensive test plans and QA checklists based on requirements documents, ensuring thorough software testing.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add jamesrochabrun/skills --skill qa-test-planner -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
jamesrochabrun
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned jamesrochabrun/skills at 2482c17637.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 2482c17637
- Manifest
- skills/qa-test-planner/SKILL.md
- Scanned
- 5 files, 2,084 lines
About this skill
What it does
The Qa Test Planner skill assists QA engineers in creating comprehensive testing documentation and processes. It generates test plans, manual test cases with detailed steps, regression test suites (including smoke tests), validates UI implementations against Figma designs (requires Model Context Protocol - MCP), and creates bug report templates. This helps ensure thorough software testing and improved quality assurance workflows.
When to use it
- When you need a structured approach to creating comprehensive test plans for new or existing software projects.
- To generate detailed, repeatable manual test cases quickly and consistently.
- For building regression test suites to maintain stability after code changes.
- To validate UI implementations against design specifications (if using Figma).
- When you need standardized bug report templates to improve clarity and reproducibility of issues.
Key capabilities
- Test Plan Creation: Generates comprehensive test strategies, objectives, timelines, and resource allocation plans.
- Manual Test Case Generation: Creates detailed step-by-step test cases with expected results, preconditions, and test data requirements.
- Regression Test Suite Builder: Builds smoke tests and critical path testing scenarios for regression testing.
- Figma Design Validation (with MCP): Compares UI implementations to Figma designs to identify visual discrepancies.
- Bug Report Generation: Creates clear bug report templates including reproduction steps, environment details, and expected vs. actual behavior.
Example prompts
- "Create a test plan for the user authentication module."
- "Generate manual test cases for the checkout process."
- "Build a regression test suite focusing on critical path functionality."
- “Validate the login screen against this Figma design [link to Figma file].” (Requires MCP)
Tips & gotchas
- To use the Figma Design Validation feature, you must have Model Context Protocol (MCP) enabled and provide a link to your Figma design.
- The skill generates structured test case formats; ensure that all fields are populated for maximum effectiveness.
- This is specifically designed for QA engineers performing manual testing tasks.