skills.rest
leonardoacosta
leonardoacostaCOMMUNITY
Explore all skills by this author →
GitHub

qa-test-planner

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

Updated Aug 2, 2026
Search Tags:#qa#figma#manual testing#bug report#regression testing#test cases#test plan
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill qa-test-planner-leonardoacosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-test-planner
Source: https://github.com/leonardoacosta/skills/tree/main/web-frontend-kit/skills/qa-test-planner
Command: npx skills add https://github.com/leonardoacosta/skills --skill qa-test-planner-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Manual QA work produces artifacts that automated test suites never generate: human-readable test plans, structured bug reports for trackers, regression suite definitions, and Figma-vs-implementation checklists. This Skill generates those artifacts from ready-made templates and adds judgment on when a manual finding should become an automated e2e regression test versus a tracked issue. ## Core Features & Use Cases - Template Generation: Produce test plans, step-by-step test cases, regression suites (smoke/targeted/full), and categorized bug reports (standard, UI, performance, security, crash) with severity and priority guidance. - Figma Design Validation: Build design-vs-implementation discrepancy checklists using Figma MCP queries for layout, typography, color, and component states. - Escalation Judgment: Decide whether a manual finding becomes a beads issue or a Playwright e2e spec based on severity, reproducibility, and automation cost, including which CI tag the promoted spec should carry. - Use Case: Before a release, ask for a regression suite for the checkout module, then file a bug report for a payment failure and get a recommendation on whether it warrants an automated @payments e2e test. ## Quick Start Ask the agent to use the qa-test-planner skill to create a test plan for your feature, or run the interactive scripts generate_test_cases.sh and create_bug_report.sh for guided prompts.

Frequently Asked Questions about qa-test-planner

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

FAQPage Schema
How do I write a manual QA test plan for a new feature?▼

Invoke the skill with a request like "create a test plan for checkout" to get a document covering strategy, scope, entry and exit criteria, risks, and timeline. The test case templates then break the plan into step-by-step cases with preconditions, test data, and expected results.

How do I write a good bug report with steps to reproduce?▼

Use the bug report templates, which capture severity, priority, environment, numbered reproduction steps, expected versus actual behavior, and evidence attachments. The create_bug_report.sh script walks you through each field interactively and outputs a formatted Markdown file.

When should a manual QA finding become an automated e2e test?▼

Decide on three axes: severity, reproducibility, and automation cost. High-severity, reliably reproducible, cheap-to-fixture findings should become Playwright specs immediately; low-severity or expensive-to-automate findings become tracked issues and are promoted only if they recur.

Can I compare a web page against a Figma design?▼

Yes, the Figma validation guide uses Figma MCP queries to pull design specs for layout, typography, colors, and component states, then compares them against the implementation via browser DevTools. Discrepancies are documented with a dedicated UI bug report template.

What is the difference between smoke, targeted, and full regression suites?▼

Smoke suites run 15-30 minutes covering critical paths daily, targeted suites run 30-60 minutes on changed feature areas, and full suites take 2-4 hours before releases covering all functional, integration, and UI cases. The regression guide defines execution order and pass/fail criteria for each.

When should I skip manual test planning and write automated tests directly?▼

Skip the manual plan when the flow already has stable selectors and predictable inputs, since a manual document adds no value once a Playwright spec can run on every PR. Manual planning wins for UI still in flux, one-time validations, or checks needing human design judgment.

Related Skills

Explore More Software Engineering Skills→
gihwan-devgihwan-dev
1

figma-design-pipeline

Convert Figma designs into code and validate visual fidelity.

Community
Advanced
leonardoacostaleonardoacosta

qa-test-planner

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

Community
Intermediate
aimskraimskr

testing-strategy

Design test strategies and QA plans for software features.

Official
Intermediate
swarm-ai-researchswarm-ai-research
39

run-scenario

Execute predefined SWARM simulation scenarios and export standardized results.

Official
Intermediate