qa-test-generation

Generate QA test checklists from acceptance criteria and modified files.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill qa-test-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-generation
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/qa-test-generation
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill qa-test-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate structured QA test checklists from acceptance criteria and modified files, ensuring coverage of happy path, error cases, edge cases, boundary values, empty states, and permissions.

Core Features & Use Cases

  • Generate multi-path test steps based on UI, API, and backend changes.
  • Ensure coverage for edge/error/boundary/empty/permissions scenarios.
  • Output is structured as TestStep[] and integrates with /task-complete workflow.

Quick Start

Provide the task acceptance criteria and the list of modified files to auto-generate a complete test checklist.

Frequently Asked Questions about qa-test-generation

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

FAQPage Schema
How do I generate QA test checklists from acceptance criteria?

To generate QA test checklists from acceptance criteria, provide the task criteria and a list of modified files. The system outputs a structured list of TestStep objects covering UI, API, and backend changes automatically.

What is included in an automated QA test generation checklist?

Automated QA test generation includes coverage for happy paths, error cases, edge cases, boundary values, empty states, and permission scenarios across UI, API, and backend layers to ensure comprehensive validation.

Can I generate test steps for both UI and API backend changes?

Yes, you can generate test steps for UI, API, and backend changes simultaneously. The system analyzes modified files and acceptance criteria to apply relevant test coverage across all affected application layers.

How do I create boundary value and empty state test cases automatically?

Boundary value and empty state test cases are created automatically by parsing acceptance criteria and modified files. The generation logic inherently targets these edge conditions alongside happy path and permission scenarios.

How do I save generated test steps to my existing workflow API?

Generated test steps are output as structured TestStep arrays that integrate directly with the /task-complete workflow. You can save these objects via your existing bridge or API without manual formatting.