team-qa

Coordinate QA cycles from story classification to release verdicts.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill team-qa-nuoyanruoshui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/team-qa
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill team-qa-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a structured quality assurance workflow so teams can move from feature scope to verified results, documented bugs, and a clear release decision without losing track of approvals or testing gaps.

Core Features & Use Cases

  • QA Strategy: Classify stories, assess automated and manual coverage, identify blockers, and evaluate smoke-check status.
  • Test Planning and Execution: Generate test plans and detailed manual test cases, guide approval checkpoints, and record PASS, FAIL, WARNING, or BLOCKED outcomes.
  • Bug Reporting and Sign-Off: Delegate formal bug documentation, summarize coverage and defects, and produce an approval verdict with conditions and next steps.
  • Use Case: For a sprint containing gameplay logic, UI, and integration stories, use this Skill to coordinate strategy, write test cases, conduct manual QA, file bugs, and prepare the final sign-off report.

Quick Start

Invoke the team-qa skill with a sprint identifier or feature name and select the appropriate review mode to begin an approval-driven QA cycle.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I coordinate a complete manual testing cycle for a software sprint?▼

Coordinate a complete manual testing cycle by classifying scoped stories, generating test plans, executing test cases, and recording PASS, FAIL, WARNING, or BLOCKED outcomes to produce a final sign-off verdict.

What is an approval-driven QA workflow and when do I need it for feature releases?▼

An approval-driven QA workflow requires passing structured checkpoints during test planning, execution, and bug reporting before granting a release sign-off. You need it when moving from feature scope to verified results without losing track of testing gaps or approvals.

Can I use this approach to handle blocker management and formal bug reporting?▼

Yes, you can handle blocker management and formal bug reporting by evaluating smoke-check status, recording BLOCKED outcomes during test execution, and delegating formal documentation for defects before producing an approval verdict.

Does structured QA sign-off work for sprint validation covering both UI and logic changes?▼

Structured QA sign-off works for sprint validation by classifying gameplay logic, UI, and integration stories. It assesses automated and manual coverage, evaluates smoke checks, and produces a release decision with conditions and next steps.

What are the limitations of manual test planning without automated coverage assessment?▼

Without automated coverage assessment, manual test planning risks missing approval gates and defect tracking. Structured QA workflows require evaluating both automated and manual evidence to handle blockers and produce a reliable sign-off verdict.