team-qa

Orchestrate a full QA cycle with strategy, test cases, and sign-off.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill team-qa-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill team-qa-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a messy, unstructured QA effort into a coordinated testing cycle that produces a complete QA package with strategy, test plan, test cases, manual results, bug reports, and sign-off.

Core Features & Use Cases

  • QA strategy orchestration: delegates to a QA lead to classify stories, determine automated vs manual needs, and generate a structured plan with smoke-check verdict handling.
  • Test plan & test cases pipeline: generates a sprint/feature-scoped QA plan and produces detailed manual QA test cases for the right stories.
  • Manual QA execution & bug reporting: walks through approved manual QA items, records outcomes, and files formal bugs with consistent naming.
  • QA sign-off & session update: compiles results into a sign-off report with a clear verdict (APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED) and updates the active session state.

Quick Start

Run the QA cycle for the current sprint by invoking team-qa with: /team-qa sprint-03

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I run a full QA cycle for a game development sprint?

Run a full QA cycle by orchestrating test strategy, plans, manual execution, and sign-off. A single command coordinates the entire process, delegating tasks to subagents to validate stories and file bug reports.

What is a smoke-check gate in manual QA testing?

A smoke-check gate in manual QA testing is a verdict rule that determines if a story passes basic validation before advancing. The QA orchestration process enforces these rules to ensure stories meet minimum criteria for further testing.

How do I generate test cases and a test plan for sprint features?

Generate test cases and a test plan for sprint features by running a QA orchestration cycle. The process delegates to a QA lead to classify stories, determine automated versus manual needs, and produce detailed test cases for the relevant stories.

How does bug reporting work during a manual QA workflow?

Bug reporting during a manual QA workflow occurs when test criteria fail. The QA process walks through approved manual items, records outcomes, and files formal bug reports with consistent naming conventions into production paths.

Can I get a formal QA sign-off report after testing a feature?

You can get a formal QA sign-off report after testing a feature. The QA cycle compiles manual results and bug reports into a final sign-off document with a clear verdict of APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED.

Does this QA orchestration require external testing frameworks or dependencies?

This QA orchestration requires no external testing frameworks or dependencies. It operates independently by delegating tasks to internal qa-lead and qa-tester subagents, resolving review modes, and writing structured outputs into production paths.