qa-test-planner

Generate QA test plans, manual test cases, regression suites, and bug reports.

567|82|Updated Mar 15, 2026

Search Tags:#testing #qa #figma #bug report #regression #test plan #test case

One-click install

npx skills add https://github.com/pedronauck/skills --skill qa-test-planner-pedronauck

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: qa-test-planner
Source: https://github.com/pedronauck/skills/tree/main/skills/qa-test-planner
Command: npx skills add https://github.com/pedronauck/skills --skill qa-test-planner-pedronauck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive QA documentation, including test plans, manual test cases, regression suites, and bug reports, saving QA engineers significant time and ensuring consistency.

Core Features & Use Cases

Test Plan Generation: Create detailed test plans with scope, strategy, and risks.
Test Case Creation: Generate step-by-step manual test cases with expected results.
Regression Suite Building: Define smoke, targeted, or full regression suites.
Figma Design Validation: Compare UI implementation against Figma designs.
Bug Reporting: Document bugs with clear steps, environment details, and evidence.
Use Case: A QA engineer needs to create a test plan for a new user authentication feature. They can use this Skill to generate a complete plan, then generate 10 specific test cases for login, logout, and password reset flows, ensuring all critical paths and edge cases are covered.

Quick Start

Use the qa-test-planner skill to generate 5 manual test cases for the user profile update feature.

Frequently Asked Questions about qa-test-planner

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

FAQPage Schema

How do I generate manual test cases for a new feature?▼

Yes, you can validate UI implementation against Figma designs using the Figma MCP integration. It compares your live UI components directly to the design files to identify visual discrepancies.

What's the best way to document a bug report with environment details?▼

You can build regression test suites by defining smoke, targeted, or full regression scopes. The tool structures these suites automatically based on your testing requirements to ensure coverage.

Do I need Figma to create a test plan?▼

No, you do not need Figma to create a test plan; the tool generates plans with scope, strategy, and risks independently. Figma integration is only required for design validation tasks.

What should be included in a comprehensive test plan?▼

A comprehensive test plan should include the testing scope, strategy, and identified risks. The automation tool structures these deliverables automatically to ensure consistency across QA documentation.