mcpField
T
team-quality-assurance

team-quality-assurance

github.com/catlog22Testing & quality2.1k69 installsUpdated 19w ago
Repository

About team-quality-assurance

A multi-agent QA skill for coordinating discovery, test generation, execution, and analysis. It offers discovery, testing, and full pipeline modes with parallel generation and cleanup loops.

Key features

  1. 01Scout-to-analyst role pipeline
  2. 02Discovery, testing, and full modes
  3. 03Parallel test generation
  4. 04Status checks and pipeline resume

Use cases

  1. 01Scan a project for quality issues
  2. 02Generate and execute tests
  3. 03Run a coordinated end-to-end QA cycle

MCP support

The workflow uses the `mcp__ccw-tools__team_msg` message bus to coordinate team sessions.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/catlog22/claude-code-workflow --skill team-quality-assurance

After installing, type/team-quality-assurancein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

roles/analyst/
role.md
roles/coordinator/
role.md
roles/coordinator/commands/
analyze.md
dispatch.md
monitor.md
roles/executor/
role.md
roles/generator/
role.md
roles/scout/
role.md
roles/strategist/
role.md
specs/
pipelines.md
team-config.json

Details

From the project README

Team Quality Assurance

Orchestrate multi-agent QA: scout -> strategist -> generator -> executor -> analyst. Supports discovery, testing, and full closed-loop modes with parallel generation and GC loops.

Architecture

Skill(skill="team-quality-assurance", args="task description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+-------+-------+
                    v       v       v       v       v
                 [scout] [strat] [gen] [exec] [analyst]
                 team-worker agents, each loads roles/<role>/role.md

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
scoutroles/scout/role.mdSCOUT-*false
strategistroles/strategist/role.mdQASTRAT-*false
generatorroles/generator/role.mdQAGEN-*false
executorroles/executor/role.mdQARUN-*dynamic
analystroles/analyst/role.mdQAANA-*false

Role Router

Parse $ARGUMENTS:

  • Has --role <name> -> Read roles/<name>/role.md, execute Phase 2-4
  • No --role -> @roles/coordinator/role.md, execute entry router

Shared Constants

  • Session prefix: QA
  • Session path: .workflow/.team/QA-<slug>-<date>/
  • Team name: quality-assurance
  • CLI tools: ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
  • Message bus: mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker Spawn Template

Coordinator spawns workers using this template:

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: "quality-assurance",
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: quality-assurance
requirement: <task-description>
inner_loop: <true|false>

## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.

Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

User Commands

CommandAction
check / statusView pipeline status graph
resume / continueAdvance to next step
--mode=discoveryForce discovery mode
--mode=testingForce testing mode
--mode=fullForce full QA mode

Completion Action

When pipeline completes, coordinator presents:

AskUserQuestion({
  questions: [{
    question: "Quality Assurance pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export deliverables to target directory" }
    ]
  }]
})

Session Directory

.workflow/.team/QA-<slug>-<date>/
├── .msg/messages.jsonl     # Team message bus
├── .msg/meta.json          # Session state + shared memory
├── wisdom/                 # Cross-task knowledge
├── scan/                   # Scout output
├── strategy/               # Strategist output
├── tests/                  # Generator output (L1/, L2/, L3/)
├── results/                # Executor output
└── analysis/               # Analyst output

Specs Reference

Error Handling

ScenarioResolution
Unknown --role valueError with available role list
Role not foundError with expected path (roles//role.md)
CLI tool failsWorker fallback to direct implementation
Scout finds no issuesReport clean scan, skip to testing mode
GC loop exceededAccept current coverage with warning
Fast-advance conflictCoordinator reconciles on next callback
Completion action failsDefault to Keep Active

Comments

Markdown supported