skills.rest
striderZA
striderZACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-qa

Coordinate QA strategy, test planning, manual execution, and sign-off reporting.

72|7|Updated Apr 29, 2026
Search Tags:#quality gate#sign-off#test plan#bug reporting#smoke testing#sprint workflow#qa orchestration
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-qa-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/team-qa
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-qa-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating QA across strategy, manual testing, and bug sign-off can stall releases when coverage, smoke checks, or acceptance criteria are unclear; this Skill organizes the QA team into a structured, decision-gated workflow so a sprint or feature can ship with confidence.

Core Features & Use Cases

  • End-to-end QA orchestration: Coordinates qa-lead (strategy + test plan + sign-off) and qa-tester (test cases + bug reporting) to produce a complete QA package.
  • Story-scoped testing: Automatically detects in-scope stories from sprint identifiers, system-tagged features, or inferred active sprint/session state.
  • Smoke check gate with verdicts: Evaluates smoke test scenarios from tests/smoke/ and blocks advancement when smoke check fails.
  • Manual QA execution and bug filing: Runs manual verification in batches, collects PASS/PASS WITH NOTES/FAIL/BLOCKED decisions, and writes formal bug reports for failures.
  • Final QA sign-off report: Produces an APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED verdict based on severity rules and documented issues.

Example use case: You’re preparing to launch sprint-03 and need a QA plan, test cases, manual walkthrough instructions, and a final sign-off report with bugs filed if critical issues are found.

Quick Start

Run the team-qa skill with an argument like sprint-03 or feature: system-name to generate a complete QA cycle with strategy, test plan, manual QA execution guidance, and a sign-off verdict.

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 complete QA cycle for a sprint?▼

You orchestrate a sprint QA cycle by coordinating strategy, test planning, manual execution, and sign-off. This workflow reads in-scope stories, generates test cases, executes manual verification, and files formal bug reports to produce a final sign-off verdict.

What is a smoke check gate in sprint QA workflow?▼

A smoke check gate evaluates smoke test scenarios from the tests/smoke directory and blocks QA advancement when a smoke check fails. This hard stop ensures critical baseline functionality works before proceeding to manual QA execution and deeper testing.

How do I generate test cases and a QA plan from user stories?▼

Generate a QA plan and test cases by reading story scope from production directories using sprint identifiers or system-tagged features. The workflow coordinates a qa-lead for strategy and a qa-tester for case generation and bug reporting.

How are bug reports filed during manual QA execution?▼

During manual QA execution, the workflow collects PASS, PASS WITH NOTES, FAIL, or BLOCKED decisions for each test case. When failures occur, it writes formal bug reports with structured severity outcomes for the final sign-off evaluation.

How does a QA sign-off report decide sprint approval?▼

A QA sign-off report produces an APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED verdict based on severity rules and documented issues. This final report aggregates all manual testing outcomes and filed bug reports to determine release readiness.

Can I scope QA testing to specific features instead of an entire sprint?▼

Yes, you can scope QA testing by passing a feature identifier like feature: system-name. The workflow automatically detects in-scope stories from sprint identifiers, system-tagged features, or inferred active sprint and session state.

Related Skills

Explore More Product & Management Skills→
sethdfordsethdford
2

Sprint Planning Assistant

Generate sprint plans and risk assessments from team capacity and velocity.

Community
Advanced
Euraika-LabsEuraika-Labs
14

team-qa

Orchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.

Official
Advanced
0xMerl990xMerl99
1

jira

Manage Jira issues, sprints, workflows, and JQL reporting.

Community
Intermediate
jmaglyjmagly
175

gate-evaluation

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

Community
Advanced