Agent skill
team-quality-assurance
Unified team skill for quality assurance. Full closed-loop QA combining issue discovery and software testing. Triggers on "team quality-assurance", "team qa".
Install this agent skill to your Project
npx add-skill https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/team-quality-assurance
SKILL.md
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 | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| scout | roles/scout/role.md | SCOUT-* | false |
| strategist | roles/strategist/role.md | QASTRAT-* | false |
| generator | roles/generator/role.md | QAGEN-* | false |
| executor | roles/executor/role.md | QARUN-* | true |
| analyst | roles/analyst/role.md | QAANA-* | false |
Role Router
Parse $ARGUMENTS:
- Has
--role <name>-> Readroles/<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:
| Tool Call | Verdict | Reason |
|---|---|---|
spawn_agent, wait_agent, close_agent, send_message, assign_task |
ALLOWED | Orchestration |
list_agents |
ALLOWED | Agent health check |
request_user_input |
ALLOWED | User interaction |
mcp__ccw-tools__team_msg |
ALLOWED | Message bus |
Read/Write on .workflow/.team/ files |
ALLOWED | Session state |
Read on roles/, commands/, specs/ |
ALLOWED | Loading own instructions |
Read/Grep/Glob on project source code |
BLOCKED | Delegate to worker |
Edit on any file outside .workflow/ |
BLOCKED | Delegate to worker |
Bash("ccw cli ...") |
BLOCKED | Only workers call CLI |
Bash running build/test/lint commands |
BLOCKED | Delegate to worker |
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-<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:
spawn_agent({
agent_type: "team_worker",
task_name: "<task-id>",
fork_context: false,
items: [
{ type: "text", text: `## 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.` },
{ type: "text", text: `## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>` },
{ type: "text", text: `## Upstream Context
<prev_context>` }
]
})
After spawning, use wait_agent({ targets: [...], timeout_ms: 900000 }) to collect results, then close_agent({ target }) each worker.
Model Selection Guide
| Role | model | reasoning_effort | Rationale |
|---|---|---|---|
| Scout (SCOUT-*) | (default) | medium | Issue discovery scanning, less reasoning needed |
| Strategist (QASTRAT-*) | (default) | high | Test strategy design requires deep analysis |
| Generator (QAGEN-*) | (default) | high | Test code generation needs precision |
| Executor (QARUN-*) | (default) | medium | Running tests and collecting results |
| Analyst (QAANA-*) | (default) | high | Quality analysis and coverage assessment |
Override model/reasoning_effort in spawn_agent when cost optimization is needed:
spawn_agent({
agent_type: "team_worker",
task_name: "<task-id>",
fork_context: false,
model: "<model-override>",
reasoning_effort: "<effort-level>",
items: [...]
})
User Commands
| Command | Action |
|---|---|
check / status |
View pipeline status graph |
resume / continue |
Advance to next step |
--mode=discovery |
Force discovery mode |
--mode=testing |
Force testing mode |
--mode=full |
Force full QA mode |
v4 Agent Coordination
Message Semantics
| Intent | API | Example |
|---|---|---|
| Send scout findings to running strategist | send_message |
Queue issue scan results to QASTRAT-* |
| Not used in this skill | assign_task |
No resident agents -- all workers are one-shot |
| Check running agents | list_agents |
Verify agent health during resume |
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({}) in handleResume and handleComplete:
// 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>" enabling direct addressing:
send_message({ target: "QASTRAT-001", items: [...] })-- queue scout findings to running strategistclose_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-<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
- specs/pipelines.md — Pipeline definitions and task registry
- specs/team-config.json — Team configuration and shared memory schema
Error Handling
| Scenario | Resolution |
|---|---|
| Unknown --role value | Error with available role list |
| Role not found | Error with expected path (roles//role.md) |
| CLI tool fails | Worker fallback to direct implementation |
| Scout finds no issues | Report clean scan, skip to testing mode |
| GC loop exceeded | Accept current coverage with warning |
| Fast-advance conflict | Coordinator reconciles on next callback |
| Completion action fails | Default to Keep Active |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
investigate
Chain-loaded investigation. 5-phase Iron Law methodology with root cause gate.
workflow-plan
Chain-loaded workflow planning. 6-phase with mode routing and conflict detection.
review-cycle
Chain-loaded review cycle. 3-mode routing for session, module, or fix review.
workflow-tdd-plan
Chain-loaded TDD planning. 7-phase with Red-Green-Refactor task generation.
spec-generator
Chain-loaded spec generation. 8-phase with quality gate loop and auto-fix.
brainstorm
Chain-loaded brainstorming. 4-phase dual-mode with auto multi-role and single-role paths.
Didn't find tool you were looking for?