team-qa

Coordinate QA teams through sprint-wide planning, execution, and sign-off workflows.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill team-qa-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill team-qa-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the QA workflow end-to-end for a sprint or feature by coordinating qa-lead, qa-tester, and stakeholders into a cohesive, efficient process.

Core Features & Use Cases

  • Phase-driven QA pipeline: load context, strategy, test plan generation, test case writing, manual QA, and sign-off reporting.
  • Role coordination: align qa-lead strategy with qa-tester execution and stakeholder reviews.
  • Artifact generation: produce test plans, test cases, burn-downs, and a final sign-off report for sprint deliverables.

Quick Start

Invoke the skill with a sprint identifier or feature name to begin the 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 QA testing cycle for a sprint?

You coordinate a sprint QA cycle by orchestrating phase-driven workflows that guide context loading, test plan generation, manual QA execution, and final sign-off reporting across QA leads, testers, and stakeholders.

What is phase-driven QA orchestration for feature testing?

Phase-driven QA orchestration is a structured workflow that organizes feature testing into sequential decision gates, spanning strategy, test plan creation, manual execution, and artifact generation to align QA leads with testers.

How do I generate test plans and bug reports for sprint deliverables?

You generate test plans and bug reports for sprint deliverables by running a structured QA workflow that produces artifacts like test cases, burn-downs, and final sign-off reports through delegated tasks and decision gates.

Can I use this QA workflow for both sprint and feature-level testing?

Yes, you can use this QA workflow for both sprint and feature-level testing, as it applies phase-driven orchestration, task delegation, and artifact generation across strategy, smoke checks, and sign-off for either scope.

What's the best way to align QA leads, testers, and stakeholders during testing?

The best way to align QA leads, testers, and stakeholders is to use role coordination within a structured QA pipeline, ensuring strategy from leads matches execution by testers and reviews by stakeholders through decision gates.

What artifacts are produced at the end of a QA sign-off process?

The artifacts produced at the end of a QA sign-off process include comprehensive test plans, written test cases, burn-downs, and a final sign-off report that satisfies sprint deliverable requirements.