qa-report

Generate structured QA plans, test cases, regression suites, and bug reports from feature requirements.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill qa-report-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/haryelramalho/skills/tree/main/skills/curated/qa-report
Command: npx skills add https://github.com/haryelramalho/skills --skill qa-report-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps QA teams turn feature requirements into clear, reusable testing artifacts instead of improvising plans, test cases, and bug writeups from scratch.

Core Features & Use Cases

  • Test Planning: Creates structured test plans, regression suites, and coverage guidance for a feature or release.
  • Test Case Authoring: Produces detailed functional, UI, integration, security, and performance test cases with priorities and automation annotations.
  • Figma Validation: Compares implementation against design specs and documents visual mismatches as test cases or bug reports.
  • Bug Reporting: Generates reproducible, template-driven defect reports with environment, impact, and follow-up details.
  • Use Case: A QA engineer can use this Skill to define release regression coverage, document edge cases, and prepare handoff-ready issues for execution.

Quick Start

Ask this skill to generate QA test cases, a test plan, or a bug report for the feature you want to validate.

Frequently Asked Questions about qa-report

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

FAQPage Schema
How do I generate test cases from feature requirements?

To generate test cases from feature requirements, provide the feature details to create structured functional, UI, integration, security, and performance test cases with priorities and automation annotations.

What is the best way to plan regression testing for a product change?

Plan regression testing for a product change by generating structured test plans and regression suites directly from feature requirements to ensure comprehensive release coverage.

Can I validate implementation against Figma designs during test planning?

Yes, you can validate implementation against Figma designs by comparing specs and documenting visual mismatches as test cases or bug reports, using optional Figma MCP or browser validation.

How do I write reproducible bug reports from feature requirements?

Write reproducible bug reports by using template-driven markdown artifacts that document environment details, impact, and follow-up steps for product defects.

Do I need shared directories to manage QA test plans and bug reports?

Yes, shared QA output directories are required to store the template-based markdown artifacts generated for test plans, test cases, and bug reports.