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

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

Delegation Lock

Coordinator is a PURE ORCHESTRATOR. It coordinates, it does NOT do.

Before calling ANY tool, apply this check:

spawn_agent

wait_agent

close_agent

send_message

followup_task

list_agents

request_user_input

mcp__ccw-tools__team_msg

Read/Write

.workflow/.team/

Read

roles/

commands/

specs/

Read/Grep/Glob

Edit

.workflow/

Bash("ccw cli ...")

Bash

If a tool call is BLOCKED: STOP. Create a task, spawn a worker.

No exceptions for "simple" tasks. Even a single-file read-and-report MUST go through spawn_agent.

Shared Constants

• Session prefix:

  QA

• Session path:

  .workflow/.team/QA-<date>-<slug>/

• 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:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  message: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
requirement: <task-description>
inner_loop: <true|false>

Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.

## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>

## Upstream Context
<prev_context>`
})

After spawning, use

wait_agent({ timeout_ms: 1800000 })

result.timed_out

close_agent({ target })

Model Selection Guide

Override model/reasoning_effort in spawn_agent when cost optimization is needed:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  model: "<model-override>",
  reasoning_effort: "<effort-level>",
  message: "..."
})

User Commands

check

status

resume

continue

--mode=discovery

--mode=testing

--mode=full

v4 Agent Coordination

Message Semantics

send_message

followup_task

list_agents

Pipeline Pattern

Sequential pipeline with GC loops: scout -> strategist -> generator -> executor -> analyst. The executor/generator may loop via GC fix tasks when coverage is below target (max 3 rounds).

Agent Health Check

Use

list_agents({})

// Reconcile session state with actual running agents
const running = list_agents({})
// Compare with tasks.json active_agents
// Reset orphaned tasks (in_progress but agent gone) to pending

Named Agent Targeting

Workers are spawned with

task_name: "<task-id>"

• send_message({ target: "QASTRAT-001", message: "..." })

  -- queue scout findings to running strategist

• close_agent({ target: "SCOUT-001" })

  -- cleanup by name after completion

Completion Action

When pipeline completes, coordinator presents:

functions.request_user_input({
  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" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export deliverables to target directory" }
    ]
  }]
})

Session Directory

.workflow/.team/QA-<date>-<slug>/
├── .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

• specs/pipelines.md — Pipeline definitions and task registry
• specs/team-config.json — Team configuration and shared memory schema

Error Handling