Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
A comprehensive Claude Code skill for QA engineers to generate test plans, manual test cases, regression test suites, Figma design validations, and structured bug reports.
The QA Test Planner skill helps quality assurance professionals create thorough, well-structured testing documentation quickly and consistently. It eliminates the repetitive work of formatting test plans and cases while ensuring best practices are followed for test coverage, bug reporting, and design validation.
Use the QA Test Planner skill when you need to:
This skill uses explicit triggering - it must be called by name:
/qa-test-planner
qa-test-planner
use the skill qa-test-planner
The QA Test Planner follows a three-phase workflow:
Creates complete test plans including:
Generates structured test cases with:
Builds tiered test suites:
Integrates with Figma MCP to:
Generates structured bug reports with:
Input:
/qa-test-planner
Create a test plan for the user authentication feature
Output: A complete test plan document including:
Input:
/qa-test-planner
Generate 5 manual test cases for the checkout flow
Output: Five numbered test cases covering:
Each includes preconditions, step-by-step instructions, expected results, test data, and edge cases.
Input:
/qa-test-planner
Build a smoke test suite for the payment module
Output: A prioritized smoke test suite (15-30 min execution) with:
Input:
/qa-test-planner
Compare the login page against the Figma design at [Figma URL]
Output: A validation checklist comparing:
Plus test cases to verify each element and document discrepancies.
Input:
/qa-test-planner
Create a bug report for: Form validation doesn't prevent submission when email field is empty
Output: A structured bug report with:
The skill includes bash scripts for guided test case and bug report creation:
./scripts/generate_test_cases.sh
Prompts for:
./scripts/create_bug_report.sh
Prompts for:
The skill includes comprehensive reference guides in the references/ directory:
The skill helps you avoid common testing mistakes:
| Avoid | Why It's Bad | What to Do Instead | |-------|--------------|-------------------| | Vague test steps | Can't reproduce consistently | Use specific actions with expected results | | Missing preconditions | Tests fail unexpectedly | Document all setup requirements | | No test data | Testers get blocked | Provide sample data or generation instructions | | Generic bug titles | Hard to track and prioritize | Be specific: "[Feature] issue when [action]" | | Skipping edge cases | Miss critical bugs | Include boundary values, nulls, empty states |
When Figma MCP is configured, the skill can:
Example Query:
Get button specifications from Figma design [URL]
Returns:
qa-test-planner/
├── README.md # This file
├── SKILL.md # Main skill definition and templates
├── references/
│ ├── test_case_templates.md # Test case formats
│ ├── bug_report_templates.md # Bug documentation templates
│ ├── regression_testing.md # Regression suite strategies
│ └── figma_validation.md # Design validation workflows
└── scripts/
├── generate_test_cases.sh # Interactive test case generator
└── create_bug_report.sh # Interactive bug report creator
All deliverables are generated in Markdown format for easy copy-paste into:
The structured format ensures consistency across your team and makes test documentation searchable and maintainable.
Typical time to create documentation:
| Deliverable | Manual Time | With Skill | Time Saved | |-------------|-------------|------------|------------| | Test Plan | 2-3 hours | 10-15 min | 90% | | 10 Test Cases | 1-2 hours | 5-10 min | 85% | | Regression Suite | 2-4 hours | 15-20 min | 90% | | Bug Report | 10-15 min | 5 min | 50% | | Figma Validation | 30-60 min | 10-15 min | 75% |
/qa-test-plannerFor detailed information on specific deliverables, see SKILL.md which includes:
"Testing shows the presence, not the absence of bugs." - Edsger Dijkstra
"Quality is not an act, it is a habit." - Aristotle
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Category:developer