Team PlanEx
Unified team skill: plan-and-execute pipeline for issue-based development. Built on team-worker agent architecture — coordinator orchestrates, workers are team-worker agents loading role-specific instructions from roles/<role>/role.md.
Architecture
Skill(skill="team-planex", 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
[planner] [executor]
(team-worker agent, (team-worker agent,
loads roles/planner/role.md) loads roles/executor/role.md)
Role Registry
| Role |
Path |
Prefix |
Inner Loop |
| coordinator |
roles/coordinator/role.md |
— |
— |
| planner |
roles/planner/role.md |
PLAN-* |
true |
| executor |
roles/executor/role.md |
EXEC-* |
true |
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:
PEX
- Session path:
.workflow/.team/PEX-<slug>-<date>/
- 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: "planex",
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: planex
requirement: <task-description>
inner_loop: <true|false>
execution_method: <codex|gemini>
## 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
| Command |
Action |
check / status |
View execution status graph |
resume / continue |
Advance to next step |
add <issue-ids or --text '...' or --plan path> |
Append new tasks to planner queue |
Session Directory
.workflow/.team/PEX-<slug>-<YYYY-MM-DD>/
├── .msg/
│ ├── messages.jsonl # Message bus log
│ └── meta.json # Session state
├── task-analysis.json # Coordinator analyze output
├── artifacts/
│ └── solutions/ # Planner solution output per issue
│ ├── <issueId-1>.json
│ └── <issueId-N>.json
└── wisdom/ # Cross-task knowledge
├── learnings.md
├── decisions.md
├── conventions.md
└── issues.md
Specs Reference
- specs/pipelines.md — Pipeline definitions, task metadata registry, execution method selection
Error Handling
| Scenario |
Resolution |
| Unknown command |
Error with available command list |
| Role not found |
Error with role registry |
| Role spec file not found |
Error with expected path (roles//role.md) |
| team-worker agent unavailable |
Error: requires .claude/agents/team-worker.md |
| Planner issue planning failure |
Retry once, then skip to next issue |
| Executor impl failure |
Report to coordinator, continue with next EXEC-* task |
| Pipeline stall |
Coordinator monitors, escalate to user |
| Worker no response |
Report waiting task, suggest user resume |
1---2name: team-planex-23description: Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on "team planex".4allowed-tools: Agent(*), TaskCreate(*), TaskList(*), TaskGet(*), TaskUpdate(*), TeamCreate(*), TeamDelete(*), SendMessage(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ccw-tools__team_msg(*)5metadata:6 source: https://skillmd.com/skills/catlog22/team-planex-27---89# Team PlanEx1011Unified team skill: plan-and-execute pipeline for issue-based development. Built on **team-worker agent architecture** — coordinator orchestrates, workers are team-worker agents loading role-specific instructions from `roles/<role>/role.md`.1213## Architecture1415```16Skill(skill="team-planex", args="task description")17 |18 SKILL.md (this file) = Router19 |20 +--------------+--------------+21 | |22 no --role flag --role <name>23 | |24 Coordinator Worker25 roles/coordinator/role.md roles/<name>/role.md26 |27 +-- analyze -> dispatch -> spawn workers -> STOP28 |29 +---------------+---------------+30 v v31 [planner] [executor]32 (team-worker agent, (team-worker agent,33 loads roles/planner/role.md) loads roles/executor/role.md)34```3536## Role Registry3738| Role | Path | Prefix | Inner Loop |39|------|------|--------|------------|40| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |41| planner | [roles/planner/role.md](roles/planner/role.md) | PLAN-* | true |42| executor | [roles/executor/role.md](roles/executor/role.md) | EXEC-* | true |4344## Role Router4546Parse `$ARGUMENTS`:47- Has `--role <name>` → Read `roles/<name>/role.md`, execute Phase 2-448- No `--role` → `@roles/coordinator/role.md`, execute entry router4950## Shared Constants5152- **Session prefix**: `PEX`53- **Session path**: `.workflow/.team/PEX-<slug>-<date>/`54- **CLI tools**: `ccw cli --mode analysis` (read-only), `ccw cli --mode write` (modifications)55- **Message bus**: `mcp__ccw-tools__team_msg(session_id=<session-id>, ...)`5657## Worker Spawn Template5859Coordinator spawns workers using this template:6061```62Agent({63 subagent_type: "team-worker",64 description: "Spawn <role> worker",65 team_name: "planex",66 name: "<role>",67 run_in_background: true,68 prompt: `## Role Assignment69role: <role>70role_spec: <skill_root>/roles/<role>/role.md71session: <session-folder>72session_id: <session-id>73team_name: planex74requirement: <task-description>75inner_loop: <true|false>76execution_method: <codex|gemini>7778## Progress Milestones79session_id: <session-id>80Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).81Report blockers immediately via team_msg type="blocker".82Report completion via team_msg type="task_complete" after final SendMessage.8384Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.85Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`86})87```8889## User Commands9091| Command | Action |92|---------|--------|93| `check` / `status` | View execution status graph |94| `resume` / `continue` | Advance to next step |95| `add <issue-ids or --text '...' or --plan path>` | Append new tasks to planner queue |9697## Session Directory9899```100.workflow/.team/PEX-<slug>-<YYYY-MM-DD>/101├── .msg/102│ ├── messages.jsonl # Message bus log103│ └── meta.json # Session state104├── task-analysis.json # Coordinator analyze output105├── artifacts/106│ └── solutions/ # Planner solution output per issue107│ ├── <issueId-1>.json108│ └── <issueId-N>.json109└── wisdom/ # Cross-task knowledge110 ├── learnings.md111 ├── decisions.md112 ├── conventions.md113 └── issues.md114```115116## Specs Reference117118- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions, task metadata registry, execution method selection119120## Error Handling121122| Scenario | Resolution |123|----------|------------|124| Unknown command | Error with available command list |125| Role not found | Error with role registry |126| Role spec file not found | Error with expected path (roles/<name>/role.md) |127| team-worker agent unavailable | Error: requires .claude/agents/team-worker.md |128| Planner issue planning failure | Retry once, then skip to next issue |129| Executor impl failure | Report to coordinator, continue with next EXEC-* task |130| Pipeline stall | Coordinator monitors, escalate to user |131| Worker no response | Report waiting task, suggest user `resume` |