team-qa

Orchestrate a QA cycle from strategy through sign-off with approval gates.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill team-qa-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/team-qa
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill team-qa-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a sprint or feature into a structured QA cycle, reducing the risk of missed acceptance criteria, inconsistent testing, and untracked defects. It helps a team move from initial QA strategy to evidence-backed sign-off with clear approval gates.

Core Features & Use Cases

  • QA Strategy Orchestration: Classifies stories, identifies automation versus manual validation needs, and flags blockers before testing starts.
  • Test Planning and Review: Produces a QA plan that covers scope, entry and exit criteria, smoke checks, and out-of-scope decisions.
  • Manual QA Execution Support: Generates test cases, guides manual verification, and records pass, fail, warning, or blocked outcomes.
  • Bug Reporting and Sign-Off: Captures defects with severity and produces a final QA verdict with conditions or next-step guidance.
  • Use Case: A release manager can use this Skill to coordinate QA for a feature branch, confirm smoke readiness, test the highest-risk stories, and publish a sign-off report for stakeholders.

Quick Start

Use the team-qa skill to review the current sprint or feature, approve the proposed QA strategy, and let it generate the test plan before any QA files are written.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I run structured manual QA testing for a sprint release?

Run structured manual QA testing by orchestrating a complete cycle from strategy through sign-off, classifying stories, generating test cases, and recording pass, fail, warning, or blocked outcomes. A QA lead coordinates testers to execute manual verification.

What is included in a QA test plan for feature sign-off?

A QA test plan for feature sign-off includes testing scope, entry and exit criteria, smoke checks, and out-of-scope decisions. It also identifies automation versus manual validation needs and flags blockers before testing starts.

How do I manage bug reporting and approval gates during manual testing?

Manage bug reporting and approval gates by capturing defects with severity levels and enforcing user approval at each QA phase. The cycle writes QA artifacts only after consent, producing a final sign-off verdict with conditions.

Can I use this QA cycle for game testing workflows?

Yes, you can use this QA cycle for game testing workflows. The orchestration applies to both product and game testing workflows that require story classification, smoke checks, manual test cases, and structured approval gates.

What's the best way to coordinate QA leads and testers for test execution?

Coordinate QA leads and testers by using subagents that enforce user approval at each phase. The lead classifies stories and plans scope, while the tester generates test cases and records verification outcomes.