Quality Team

How It Works

1. QA gate / coverage check: Pre-release quality assurance or coverage remediation
2. Preflight baseline: Run suite with coverage — record %, failures, uncovered modules
3. Spawn 3 agents
4. Synthesize and act: Apply P0/P1 fixes · re-run tests · re-measure coverage delta
5. QA gate: Coverage held · all P0/P1 resolved · explicit counts
6. QA gate summary: Coverage before/after · findings by severity · dead code list

Invocation Triggers

Use Cases

• Run a comprehensive QA gate before a major release
• Remediate test coverage gaps in an existing codebase
• Get a code review + test audit in parallel

The Problem

Running quality checks after the fact is reactive. By the time CI tells you about a coverage gap, the code is in review. By the time a security issue surfaces, it is in production. Quality Team runs before merge — not as a formality, but as a blocking gate with three agents each focused on a different failure mode.

What It Does

1. 1
   Preflight — run baseline coverage

   Runs the full test suite with coverage before spawning any agents. Establishes the baseline so the delta is measurable.

2. 2
   Spawn 3 agents in parallel

   Test Writer, Code Reviewer, and Coverage Analyst are dispatched simultaneously. Each has a distinct mandate — no overlap, no diffusion.

3. 3
   Test Writer fills gaps

   Identifies modules with < 80% coverage or no tests. Writes new test files prioritizing critical business logic. >= 3 real assertions per file. Runs tests to confirm all pass.

4. 4
   Code Reviewer fixes security issues

   Reviews recent changes for OWASP Top 10, hardcoded secrets, missing input validation, and injection risks. P0/P1 issues are fixed directly — not documented for later.

5. 5
   Coverage Analyst maps risk

   Identifies the 10 riskiest uncovered paths, flags dead code candidates, and assesses whether integration tests hit real dependencies or mock everything.

What You Get / What It Doesn't Do

Tips

Get the Skill

Commonly Used With