team-qa

Orchestrate an end-to-end QA cycle with strategy, test plan, cases, and sign-off.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill team-qa-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/easonlao/jiazi-game --skill team-qa-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you coordinate a QA team to generate a complete sprint/feature QA package, including strategy, test plan, test cases, manual execution, bug reporting, and a final sign-off report.

Core Features & Use Cases

  • End-to-end QA orchestration: Drives a structured testing cycle with clear phase transitions and approval gates.
  • QA strategy and smoke checks: Produces story classifications, determines automated vs manual evidence needs, and performs a smoke check gate with explicit PASS/WARN/FAIL outcomes.
  • Test plan and test case production: Creates a structured QA plan and delegates detailed manual test case writing to a tester subagent.
  • Manual QA execution and bug filing: Collects PASS/PASS WITH NOTES/FAIL/BLOCKED results, captures failure descriptions, and writes bug reports with standardized IDs.
  • Sign-off reporting: Produces a sprint/feature QA sign-off report with verdict logic and next-step guidance.

Quick Start

Invoke /team-qa with the argument "feature: system-name" to generate a full QA strategy and plan for the stories tagged to that system, stopping for user approval at each phase transition.

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 complete manual QA cycle for a sprint feature with sign-off approvals?

To run a complete manual QA cycle, this Skill orchestrates strategy creation, test planning, manual execution, bug reporting, and final sign-off, pausing at each phase for explicit user approval before proceeding.

What is a smoke check gate in QA testing and when is it needed?

A smoke check gate in QA testing validates critical functionality before deep testing, returning PASS, WARN, or FAIL outcomes to enforce conditional stopping when smoke scenarios fail or critical blockers emerge.

How do I generate a structured test plan and delegate test case writing for a feature?

You generate a structured test plan by defining story classifications and evidence needs, then delegating detailed manual test case writing to a tester subagent through task-based subagent delegation.

Does this QA orchestration workflow support story-scoped game development sprints?

Yes, this QA orchestration workflow supports story-scoped game development by loading scope from production sprints or session sprint status and applying targeted test plans and smoke-check scenarios.

How are bug reports filed during manual QA execution?

Bug reports are filed during manual QA execution by capturing PASS, FAIL, or BLOCKED results, recording failure descriptions, and assigning standardized bug IDs to track issues systematically.

What does a QA sign-off report include at the end of a testing cycle?

A QA sign-off report includes the final testing verdict logic, aggregated manual QA results, identified blockers, and next-step guidance to determine sprint or feature release readiness.