qa-report

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

Updated May 15, 2026
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill qa-report-jbonfim
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/qa-report
Command: npx skills add https://github.com/JBonfim/skill-developer --skill qa-report-jbonfim

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps teams translate product changes and design intent into clear, structured QA outputs (test plans, test cases, regression suites, Figma validation checks, and bug reports) so QA engineers can execute consistently and efficiently.

Core Features & Use Cases

  • Test plans: Produces a full test plan with objectives, scope, test strategy, automation strategy, environment requirements, entry/exit criteria, risk assessment, and timeline.
  • Test cases: Generates functional, UI/visual, integration, regression, security, performance, and smoke test cases with IDs and explicit automation annotations.
  • Regression suites: Builds regression suite documents with tiers (Smoke/Targeted/Full/Sanity), prioritization rules, execution order, and pass/fail criteria.
  • Figma validation support: Creates UI/visual test cases (TC-UI-*) and guides discrepancies into structured bug reports when Figma MCP is configured.
  • Bug reports: Generates bug reports (BUG-*) in the unified template, including severity, priority, environment, reproduction, expected vs actual, and automation follow-up guidance.

Quick Start

Generate a test plan and test cases for your feature by asking: "Create test plan and test cases for the new checkout flow, store everything under ./artifacts, and include UI checks against the provided Figma designs."

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 plans and test cases from product requirements?โ–ผ

To generate test plans and test cases, provide your product requirements to define objectives, scope, test strategy, and entry/exit criteria. The system outputs structured QA documentation with functional, regression, and security test cases complete with IDs and automation annotations.

What is the best way to structure regression suites for critical application flows?โ–ผ

The best way to structure regression suites is by organizing tests into tiers like Smoke, Targeted, Full, and Sanity. The system applies prioritization rules, execution order, and pass/fail criteria to ensure comprehensive coverage for critical application flows.

Can I create UI validation checks against Figma designs for bug reporting?โ–ผ

Yes, you can create UI validation checks against Figma designs. The system generates specific UI/visual test cases and guides discrepancies into structured bug reports including severity, priority, environment, and reproduction steps when Figma MCP is configured.

How do I document an automation strategy for my QA test plan?โ–ผ

To document an automation strategy, the test plan includes explicit automation annotations on generated test cases and outlines E2E follow-ups for critical flows. This ensures QA engineers know exactly which tests require automation and how to execute them.

Do I need a specific output directory structure for QA artifacts?โ–ผ

Yes, you need a shared output directory under a specified qa-output path. The system requires following strict artifact structures, naming conventions, and template formats to ensure all generated test plans, bug reports, and regression suites are consistently organized.