team-qa

Orchestrate end-to-end QA cycles for agile software development sprints.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill team-qa-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/team-qa
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill team-qa-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating QA team members, creating test plans, writing test cases, executing manual tests, and generating sign-off reports for software sprints and features is disjointed, time-consuming, and often leads to gaps in test coverage and missed bugs.

Core Features & Use Cases

  • Multi-Role QA Orchestration: Automatically coordinates qa-lead (strategy, test planning, sign-off) and qa-tester (test case writing, bug reporting) subagents to handle all phases of the QA workflow.
  • Configurable Review Modes: Supports full, lean, and solo review modes to adjust the depth of QA gates based on project needs and timeline constraints.
  • Structured Phase-Gated Workflow: Includes user approval checkpoints at each phase transition, plus error recovery protocols that produce partial QA reports even if subagents encounter blockers.
  • Use Case: For a game development sprint with 5 new feature stories, this skill automates the entire QA process from initial strategy to final sign-off, eliminating the need for manual coordination of QA team members.

Quick Start

Invoke the team-qa skill with your sprint identifier or feature name to start a complete QA cycle for your project.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I automate QA test plan generation and manual test execution for agile sprints?

Automating QA test plan generation and manual test execution involves orchestrating multi-role subagents to handle strategy, test case writing, and bug reporting. This eliminates disjointed manual coordination by applying structured phase-gated workflows across the entire sprint cycle.

What is phase-gated quality assurance workflow for feature testing?

A phase-gated quality assurance workflow divides testing into distinct stages with user approval checkpoints at each transition. It ensures structured validation by coordinating strategy, test case writing, execution, and formal sign-off reporting sequentially.

Can I adjust the depth of QA cycles for projects with tight timeline constraints?

Yes, you can adjust QA cycle depth using configurable review modes. Full, lean, and solo modes allow you to scale the rigor of phase-gated testing gates based on your specific project needs and timeline constraints.

How do I generate partial QA sign-off reports when manual testing blockers occur?

Generating partial QA sign-off reports when blockers occur requires built-in error recovery protocols. These protocols allow subagents to handle failures gracefully and output incomplete testing documentation rather than halting the entire cycle.

Does orchestrating QA subagents support parallel test case writing and bug reporting?

Yes, orchestrating QA subagents supports parallel task spawning. This allows simultaneous test case writing and bug reporting across different features, significantly reducing the time required for comprehensive sprint validation.

What's the best way to coordinate QA lead strategy and tester execution without manual oversight?

The best way to coordinate QA lead strategy and tester execution without manual oversight is using automated multi-role orchestration. This delegates planning and sign-off to a lead role while a tester role handles test case writing and bug reporting.