team-qa

Coordinate full QA cycles for Godot/GDScript changes with sign-off reports.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill team-qa-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/team-qa
Command: npx skills add https://github.com/scomofo/dragon-forge --skill team-qa-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a complete QA testing cycle—strategy, test plans, manual execution, bug reporting, and sign-off—so sprints and feature changes can be validated systematically instead of ad hoc.

Core Features & Use Cases

  • QA Strategy + Smoke Gate: Reviews in-scope stories, classifies them, checks for existing smoke reports, and blocks the cycle if smoke check fails.
  • Test Plan + Test Case Production: Generates a structured test plan and produces detailed manual test cases where automated evidence is insufficient.
  • Manual QA Execution + Bug Reporting + Sign-off: Guides walkthroughs through approval checkpoints, files formal bug reports, and outputs a final QA verdict with next-step guidance.

Quick Start

Run team-qa with the argument sprint identifier and review each phase proposal when prompted to produce a QA plan, test cases, bug reports, and a final sign-off.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I run end-to-end sprint QA with manual test cases and sign-off?

End-to-end sprint QA coordinates strategy, smoke gating, test plan generation, manual test case execution, bug reporting, and final sign-off through user approval gates to validate feature scopes systematically.

When do I need a smoke check before executing a QA test plan?

A smoke check is needed before executing a QA test plan to review in-scope stories, classify them, check for existing smoke reports, and block the testing cycle if the smoke check fails.

How do I validate Godot and GDScript game changes during a sprint?

Validate Godot and GDScript game changes by discovering in-scope story files, producing evidence-aligned test artifacts under production/qa, and enforcing phase transitions with user approval gates.

What is the best way to generate structured bug reports from manual QA execution?

The best way to generate structured bug reports is by guiding manual QA walkthroughs through approval checkpoints, filing formal bug reports, and outputting a final QA verdict with next-step guidance.

Can I parallelize QA orchestration tasks for sprint validation?

Yes, QA orchestration supports parallelizable delegation to qa-lead and qa-tester roles, allowing concurrent test plan generation and manual execution to process sprint validation more efficiently.

What happens if a smoke test fails during sprint validation?

If a smoke test fails during sprint validation, the QA cycle is blocked to prevent proceeding with deeper test execution, ensuring only stable builds pass the smoke gate before manual testing.