qa-team

Plan and verify end-to-end and integration test strategies with TEST-PLAN.md outputs.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill qa-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-team
Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/qa-team
Command: npx skills add https://github.com/kouko/monkey-skills --skill qa-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and verify tests beyond the unit level to catch integration failures, performance cliffs, and regression risks that unit tests miss, ensuring quality is built into the process rather than bolted on afterward.

Core Features & Use Cases

  • Test Plan Authoring: Produce implementation-ready TEST-PLAN.md aligned to ISO/IEC/IEEE 29119-3 with scope, risk register, strategy, environment requirements, and explicit pass/fail criteria.
  • Strategy & Viewpoint Extraction: Select and justify a strategy (Pyramid/Trophy/Sizes) and optionally extract Japanese-style test viewpoints (VSTeP/HAYST/ゆもつよ) to drive coverage.
  • Coverage Analysis & Regression Planning: Generate prioritized coverage-gap reports, risk-based prioritization (ISTQB L×I), and regression strategies after major changes.
  • Gate-Oriented Evaluation: Orchestrate worker/evaluator agents to run SELF, MUST, SHOULD, and MAY gates using provided checklists and rubrics for deterministic verdicts.
  • Use Case: Create a regression-ready TEST-PLAN.md for a recent backend refactor, run a coverage gap audit, and produce a prioritized list of test cases for the code-team to implement.

Quick Start

Create a TEST-PLAN.md for the checkout flow with an E2E strategy, a viewpoint list, and a coverage gap audit.

Frequently Asked Questions about qa-team

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

FAQPage Schema
How do I create an E2E test strategy aligned with ISO 29119-3?

To create an E2E test strategy aligned with ISO 29119-3, generate a TEST-PLAN.md containing scope, risk register, environment requirements, and explicit pass/fail criteria using deterministic evaluator gates.

What is risk-based prioritization using ISTQB L×I for coverage gaps?

Risk-based prioritization using ISTQB L×I evaluates coverage gaps by multiplying likelihood and impact, producing a prioritized list of test cases for the code-team to implement after major changes.

How do I choose between test pyramid and test trophy strategies?

Choosing between test pyramid and test trophy strategies involves selecting and justifying an approach based on your system's integration failure risks, optionally extracting Japanese-style viewpoints like VSTeP or HAYST to drive coverage.

Can I automate regression test planning for a backend refactor?

You can automate regression test planning for a backend refactor by generating a regression-ready TEST-PLAN.md and running a prioritized coverage gap audit to identify necessary test cases.

How do deterministic evaluator gates verify integration testing?

Deterministic evaluator gates verify integration testing by orchestrating worker/evaluator agents to run SELF, MUST, SHOULD, and MAY gates using provided checklists and rubrics for deterministic verdicts.

When do I need an E2E test plan instead of unit tests?

You need an E2E test plan instead of unit tests to catch integration failures, performance cliffs, and regression risks that unit tests miss, ensuring quality is built into the process.