mcpField
T
team-testing

team-testing

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

About team-testing

team-testing is a skill for coordinating multi-agent testing, for development tasks that span test strategy through result analysis. It builds coverage across L1, L2, and L3 layers and uses Generator-Critic loops to converge on coverage.

Key features

  1. 01Multi-agent test pipeline coordination
  2. 02Strategy, generation, execution, and analysis stages
  3. 03Progressive L1, L2, and L3 coverage
  4. 04Generator-Critic coverage loop
  5. 05Task revision and feedback

Use cases

  1. 01Plan and generate layered tests
  2. 02Run tests and analyze results
  3. 03Revise test tasks based on feedback

Install

Copy the command and run it in a terminal.

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

After installing, type/team-testingin 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/strategist/
role.md
specs/
pipelines.md
team-config.json

Details

From the project README

Team Testing

Orchestrate multi-agent test pipeline: strategist -> generator -> executor -> analyst. Progressive layer coverage (L1/L2/L3) with Generator-Critic loops for coverage convergence.

Architecture

Skill(skill="team-testing", 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
                [strat] [gen]  [exec]  [analyst]
                team-worker agents, each loads roles/<role>/role.md

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
strategistroles/strategist/role.mdSTRATEGY-*false
generatorroles/generator/role.mdTESTGEN-*true
executorroles/executor/role.mdTESTRUN-*dynamic
analystroles/analyst/role.mdTESTANA-*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: TST
  • Session path: .workflow/.team/TST-<slug>-<date>/
  • Team name: testing
  • 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: "testing",
  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: testing
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
revise <TASK-ID>Revise specific task
feedback <text>Inject feedback for revision

Completion Action

When pipeline completes, coordinator presents:

AskUserQuestion({
  questions: [{
    question: "Testing 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: "Deepen Coverage", description: "Add more test layers or increase coverage targets" }
    ]
  }]
})

Session Directory

.workflow/.team/TST-<slug>-<date>/
├── .msg/messages.jsonl     # Team message bus
├── .msg/meta.json          # Session metadata
├── wisdom/                 # Cross-task knowledge
├── strategy/               # Strategist output
├── tests/                  # Generator output (L1-unit/, L2-integration/, L3-e2e/)
├── 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
GC loop exceededAccept current coverage with warning
Fast-advance conflictCoordinator reconciles on next callback
Completion action failsDefault to Keep Active

Comments

Markdown supported