skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

team-qa

Orchestrate a QA team through a full testing cycle, producing strategy, test plans, test cases, bug reports, and a sign-off verdict.

Updated Apr 9, 2026
Search Tags:#qa#sign-off#bug-reporting#test-cases#test-plan#smoke-test#qa-orchestration
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill team-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/team-qa
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill team-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual coordination burden of running QA for a sprint or feature by orchestrating QA strategy, smoke checks, test plan generation, test case authoring, manual execution, bug filing, and a final sign-off report so teams can reliably validate releases.

Core Features & Use Cases

  • Produce a QA strategy and classify stories (Logic / Integration / Visual/Feel / UI / Config/Data) and perform a repository smoke check to gate work.
  • Generate a structured test plan, spawn qa-lead and qa-tester subagents to write test cases and bug reports, and coordinate manual QA sessions with user approvals.
  • Aggregate results into a sign-off report with verdict logic (APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED) and provide recovery options for blocked agents or missing inputs.

Quick Start

Run /team-qa with a sprint identifier to orchestrate strategy, create a test plan, produce test cases, run manual QA sessions, and generate a sign-off report.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I orchestrate a full QA cycle and sign-off for a software sprint?▼

You can orchestrate a QA cycle by running the team-qa command with a sprint identifier to generate test strategies, spawn qa-lead and qa-tester subagents, manage manual QA sessions, and produce a final sign-off report.

How do I generate test plans and test cases for manual QA coordination?▼

Generating test plans and test cases is handled by spawning Task-based qa-lead and qa-tester subagents that author structured test cases and bug reports based on your classified sprint stories and smoke test results.

What files do I need to run a smoke test and generate a QA sign-off report?▼

Running a smoke test and generating a QA sign-off report requires access to project repository story files, status files, tests/smoke scenarios, and build artifacts to properly gate work and capture test verdicts.

How does QA sign-off verdict logic work for sprint releases?▼

QA sign-off verdict logic aggregates manual QA results and bug reports to output a final status of APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED, validating the release readiness for your sprint or feature scope.

Can I classify sprint stories for test plan generation by feature type?▼

Yes, you can classify sprint stories for test plan generation into categories such as Logic, Integration, Visual/Feel, UI, and Config/Data to ensure targeted test coverage and accurate QA strategy formulation.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

team-qa

Coordinate QA team execution to produce test plans, cases, bug reports, and sign-off reports.

Community
Advanced
einja-inceinja-inc
1

task-qa

Execute mandatory tests and record failure classifications for QA evidence.

Official
Advanced
sumilee-pcusumilee-pcu

team-qa

Coordinate QA subagents for strategy, test case generation, and bug reporting.

Community
Advanced
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced