team-qa

Coordinate QA lead and tester tasks to produce test plans and sign-off reports.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill team-qa-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/dnkrow/skill/tree/main/claude-global/team-qa
Command: npx skills add https://github.com/dnkrow/skill --skill team-qa-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

team-qa turns scattered QA tasks into a coordinated, end-to-end testing cycle by planning tests, writing cases, executing manual checks, filing bugs, and producing a clear sign-off report for a sprint or feature.

Core Features & Use Cases

  • QA team orchestration: coordinates qa-lead for strategy/test plan and qa-tester for test-case writing and bug reporting.
  • Test plan + test cases + execution loop: generates a structured QA plan, then produces and reviews test cases before running manual QA.
  • Smoke check gate + sign-off: performs a smoke check verdict early to prevent proceeding when critical failures are present, then produces an approval report with conditions when needed.

Quick Start

Use the /team-qa command with an argument like "sprint-03" to run a complete QA cycle for that sprint, from strategy and test plan through manual QA results and a final sign-off report.

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?

A sprint QA cycle coordinates test plan generation, manual test case authoring, walkthroughs, and bug reporting to produce a final sign-off file. You initiate the process by providing the sprint or feature scope, which drives test strategy and execution gating.

What is a smoke check gate in sprint validation?

A smoke check gate halts sprint validation progression when critical failures are detected early. It prevents proceeding with deeper manual QA execution until severity-graded outcomes verify that critical functionality passes minimum stability thresholds.

How do I generate a QA plan and test cases for feature scope?

Generate a QA plan by reading sprint or feature scope from provided arguments, then classifying stories to drive test plan generation. This produces markdown files containing structured test cases and strategy before manual execution begins.

Can I use this for manual testing and bug reporting without an external test management tool?

Yes, you can perform manual testing and bug reporting without external test management tools by generating test cases and filing bugs directly into markdown files. The orchestration cycle handles test plan generation, manual walkthroughs, and bug reporting internally.

What is included in a QA sign-off report for sprint validation?

A QA sign-off report includes approval status, conditions, and severity-graded outcomes from manual QA walkthroughs. It summarizes test plan execution results and provides a final verdict on sprint stability based on smoke check gating results.

When should I not use automated QA orchestration for bug reporting?

Avoid automated QA orchestration when manual exploratory testing is required for complex user flows, or when sprint scope cannot be clearly classified into structured test plans. The cycle requires defined feature scope to accurately generate test cases and sign-off reports.