team-qa

Featured

Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

Testing & QA 40,030 stars 5224 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

When this skill is invoked, orchestrate the QA team through a structured testing cycle. **Decision Points:** At each phase transition, use `AskUserQuestion` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase. ## Team Composition - **qa-lead** — QA strategy, test plan generation, story classification, sign-off report - **qa-tester** — Test case writing, bug report writing, manual QA documentation ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: qa-lead` — Strategy, planning, classification, sign-off - `subagent_type: qa-tester` — Test case writing and bug report writing Always provide full context in each agent's prompt (story file paths, QA plan path, scope constraints). Launch independent qa-tester tasks in parallel where possible (e.g., multiple stories in Phase 5 can be scaffolded simultaneously). ## Pipeline ### Phase 1: Load Context Before doing anything else, gather the full scope: 1. Detect the current sprint or feature scope from the argument: - If argument is a sprint identifier (e.g., `sprint-03`): read all story files in `production/sprints/[sprint]/` - If argument is `feature: [system-name]`: glob story files tagged for that system - If no argument: read `production/session-state/active.md` and `production/sprint-status.yaml` (if ...

Details

Author
Donchitos
Repository
Donchitos/Claude-Code-Game-Studios
Created
9 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Featured

team-qa

Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

126 Updated 5 days ago
striderZA
Testing & QA Listed

qa-orchestrator

Coordinates the full QA pipeline from a ticket URL to merged automated tests. Use this skill whenever the user asks to "test a feature", "cover ticket X with tests", "run the QA pipeline", mentions a Jira/Linear ticket that needs QA, or asks about the status of an in-flight QA task. Also use it when the user wants several QA stages chained together, or when they are unsure which QA skill to run next. This skill never does the work itself — it delegates to the specialised QA skills and enforces quality gates between stages.

0 Updated 5 days ago
YevheniiaQA
Testing & QA Listed

plan-qa

Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA-<N>-<slug>.md) that /execute-qa runs. The agent drives browser and shell; the human steps in only at named handoff points. Use only when the user asks to plan manual QA — never trigger automatically.

43 Updated 2 months ago
foyzulkarim