team-qa

Orchestrate QA lead and tester subagents to execute sprint testing cycles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill team-qa-nevesb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill team-qa-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrating QA across planning, test writing, execution, and reporting is slow, inconsistent, and error-prone when managed manually or in ad-hoc chat sessions. This Skill coordinates a QA lead and QA tester subagents, enforces smoke checks and approvals, and generates test plans, test cases, bug reports, and a final sign-off to streamline and standardize sprint or feature validation.

Core Features & Use Cases

  • Spawn qa-lead to classify stories, run smoke checks, estimate effort, and produce a QA strategy and plan.
  • Spawn parallel qa-tester tasks to write detailed manual test cases and generate formal bug reports when failures occur.
  • Guided, user-approved phase gating: strategy review, test plan approval, test case review, manual QA execution, and sign-off report generation.
  • Error recovery and dependency handling: surface blocked agents, offer skip/retry/stop options, and produce partial reports when needed.
  • Use case: Run a complete QA cycle for a sprint to validate readiness for release and produce a traceable QA sign-off document.

Quick Start

Use the team-qa skill to run a full QA cycle for a sprint by invoking the command /team-qa sprint-04.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I automate a complete QA cycle for a sprint?▼

To automate a sprint QA cycle, you can coordinate qa-lead and qa-tester subagents to classify stories, generate test plans, execute manual test cases, and produce a final sign-off document.

What is the best way to generate a test plan and write manual test cases?▼

Generating a test plan and writing manual test cases is handled by spawning a qa-lead for strategy and parallel qa-tester tasks to draft detailed manual test cases for user approval.

Can I enforce smoke checks and approvals before test execution?▼

Yes, you can enforce smoke checks and approvals through guided user-approved phase gating, which requires strategy review, test plan approval, and test case review before manual QA execution.

How do I handle blocked agents or errors during test execution?▼

Handling blocked agents during test execution involves built-in error recovery that surfaces blocked subagents, offers skip, retry, or stop options, and produces partial reports when needed.

Do I need read access to project files to run bug reporting and test plans?▼

Yes, running bug reporting and test plan generation requires read access to project story and test files, alongside file and user-prompt tools to manage operations and approvals.

How do I validate feature readiness and produce a traceable QA sign-off?▼

Validating feature readiness and producing a traceable QA sign-off is achieved by running a complete QA cycle that concludes with a formal sign-off report generated after manual execution.