qa

Route QA requests to the smallest report-only QA role.

Updated May 8, 2026

Search Tags:#workflow #routing #qa #evidence #handoff #quality-assurance

Ready to run

npx skills add https://github.com/ace3/skills --skill qa-ace3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ace3/skills/tree/main/skills/qa
Command: npx skills add https://github.com/ace3/skills --skill qa-ace3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill routes broad QA requests to the smallest report-only QA role, ensuring work is handed to the most appropriate specialist and that no code changes are made during routing.

Core Features & Use Cases

Route PRD analysis, test planning, and sign-off to qa-manager.
Route test-code, framework work to qa-engineer.
Route live UI/API/performance exploration to qa-tester.
Not for root-cause investigation (use diagnose); not for production fixes (use backend or frontend developers).

Quick Start

Provide a clear QA task description and let this skill determine the correct routing path.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I route a QA task to the right testing role?▼

Routing a QA task involves analyzing your request and directing it to the smallest report-only QA role, such as qa-manager, qa-engineer, or qa-tester, to ensure proper handoffs without code changes.

What is the difference between QA routing and root-cause investigation?▼

QA routing assigns work to report-only roles for analysis and test planning, whereas root-cause investigation requires a dedicated diagnose skill to identify underlying defects.

Can I use this skill to fix production code during test execution?▼

No, you cannot use this skill to fix production code. It strictly routes work to report-only QA roles and prohibits code changes, requiring dedicated developer skills for production fixes.

When do I need to route my request to a qa-tester instead of a qa-engineer?▼

You route to a qa-tester for live UI, API, or performance exploration, whereas a qa-engineer handles test-code and framework work based on the specific QA scope.

Does this QA workflow skill handle PRD analysis and test sign-off?▼

Yes, the QA workflow skill handles PRD analysis, test planning, and sign-off by routing those specific tasks directly to the qa-manager role for report-only execution.