skills.rest
Shubh2310-developer
Shubh2310-developerCOMMUNITY
Explore all skills by this author →
GitHub

qa-test-planner

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

2|Updated Jan 10, 2026
Search Tags:#quality assurance#qa#bug report#regression testing#test cases#test plan#figma validation
One-click install
npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill qa-test-planner-shubh2310-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-test-planner
Source: https://github.com/Shubh2310-developer/ENGUNITYCORE/tree/main/.claude/skills/qa-test-planner
Command: npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill qa-test-planner-shubh2310-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? QA engineers spend hours writing repetitive test documentation—test plans, step-by-step test cases, regression suites, and bug reports—often with inconsistent formats across a team. This Skill generates structured, standards-compliant QA deliverables in minutes, ensuring complete coverage and consistent formatting. ## Core Features & Use Cases - Test Plan Generation: Produces complete test plans with scope, strategy, entry/exit criteria, risk assessment, and timelines. - Manual Test Cases & Regression Suites: Creates step-by-step test cases with expected results, plus tiered regression suites (smoke, targeted, full) with execution order and pass/fail criteria. - Figma Design Validation: Integrates with Figma MCP to extract design specifications (colors, spacing, typography) and build UI validation checklists comparing implementation against designs. - Structured Bug Reports: Generates reproducible bug reports with environment details, severity/priority classification, and evidence sections. - Use Case: A QA engineer needs to test a new checkout flow. They ask for 5 test cases and a smoke regression suite, receiving numbered test cases with preconditions, steps, expected results, and edge cases ready to paste into Jira or TestRail. ## Quick Start Ask the assistant to create a test plan for your feature, for example: "Create a test plan for the user authentication 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 feature?▼

Describe the feature and request a specific number of test cases, such as "Generate 5 manual test cases for the checkout flow." Each test case includes preconditions, numbered steps with expected results, test data, priority, and edge cases. You can also run the interactive script ./scripts/generate_test_cases.sh for guided prompts.

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

Provide the bug description and the Skill generates a structured report with a specific title, severity and priority classification, numbered reproduction steps, expected versus actual behavior, environment details, and evidence placeholders. The interactive script ./scripts/create_bug_report.sh walks you through each field.

Can I validate UI implementation against Figma designs?▼

Yes, when Figma MCP is configured, the Skill extracts design specifications like colors, spacing, typography, and component states from Figma URLs. It then generates validation checklists and test cases comparing implementation against the design, and documents discrepancies as bugs.

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

Smoke suites take 15-30 minutes and cover only critical paths, run daily or per build. Targeted regression takes 30-60 minutes and covers areas affected by recent changes. Full regression takes 2-4 hours with comprehensive coverage, run weekly or before releases.

What output formats do the generated test documents use?▼

All deliverables are generated in Markdown format for direct copy-paste into tools like Jira, Linear, GitHub Issues, Confluence, Notion, TestRail, and Zephyr. The structured format keeps documentation consistent and searchable across the team.

Related Skills

Explore More Software Engineering Skills→
Lia-CreativeLia-Creative
1

story-writer

Write user stories with Dan North narrative format and numbered Given/When/Then acceptance criteria.

Official
Intermediate
tapanshahtapanshah

testrail

Synchronize Playwright test results with TestRail test runs.

Community
Advanced
rnavarychrnavarych
14

role-aqa:e2e-testing

Guide end-to-end test automation across Playwright, Cypress, Selenium, and WebdriverIO.

Community
Advanced
mscipiomscipio

atdd

Generates executable test specifications for workflows using GanttProject's Umlet integration.

Community
Intermediate