maestro-flow 0.2.0 → 0.2.2

package/.codex/skills/team-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-review
 description: "Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review."
-allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), assign_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*)
+allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*), mcp__maestro-tools__team_msg(*)
 ---
 
 # Team Review
@@ -53,7 +53,7 @@ Before calling ANY tool, apply this check:
 
 | Tool Call | Verdict | Reason |
 |-----------|---------|--------|
-| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `assign_task` | ALLOWED | Orchestration |
+| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `followup_task` | ALLOWED | Orchestration |
 | `list_agents` | ALLOWED | Agent health check |
 | `request_user_input` | ALLOWED | User interaction |
 | `mcp__maestro-tools__team_msg` | ALLOWED | Message bus |
@@ -86,9 +86,8 @@ 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
+  fork_turns: "none",
+  message: `## Role Assignment
 role: <role>
 role_spec: <skill_root>/roles/<role>/role.md
 session: <session-folder>
@@ -96,21 +95,20 @@ 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.` },
+Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
 
-    { type: "text", text: `## Task Context
+## Task Context
 task_id: <task-id>
 title: <task-title>
 description: <task-description>
-pipeline_phase: <pipeline-phase>` },
+pipeline_phase: <pipeline-phase>
 
-    { type: "text", text: `## Upstream Context
-<prev_context>` }
-  ]
+## Upstream Context
+<prev_context>`
 })
 ```
 
-After spawning, use `wait_agent({ targets: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
+After spawning, use `wait_agent({ timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
 
 
 ### Model Selection Guide
@@ -126,10 +124,10 @@ 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,
+  fork_turns: "none",
   model: "<model-override>",
   reasoning_effort: "<effort-level>",
-  items: [...]
+  message: "..."
 })
 ```
 
@@ -152,7 +150,7 @@ spawn_agent({
 | Intent | API | Example |
 |--------|-----|---------|
 | Send scan findings to running reviewer | `send_message` | Queue scan results to REV-* as supplementary context |
-| Not used in this skill | `assign_task` | No resident agents -- sequential 3-stage pipeline |
+| Not used in this skill | `followup_task` | No resident agents -- sequential 3-stage pipeline |
 | Check running agents | `list_agents` | Verify agent health during resume |
 
 ### Pipeline Pattern
@@ -173,7 +171,7 @@ const running = list_agents({})
 ### Named Agent Targeting
 
 Workers are spawned with `task_name: "<task-id>"` enabling direct addressing:
-- `send_message({ target: "REV-001", items: [...] })` -- queue scan findings to running reviewer
+- `send_message({ target: "REV-001", message: "..." })` -- queue scan findings to running reviewer
 - `close_agent({ target: "SCAN-001" })` -- cleanup by name after completion
 
 ## Completion Action

package/.codex/skills/team-review/roles/coordinator/commands/monitor.md

@@ -32,6 +32,16 @@ Read-only status report from tasks.json, then STOP.
 1. Read tasks.json
 2. Count tasks by status (pending, in_progress, completed, failed)
 
+```javascript
+// Read progress and blocker messages from message bus
+const progressMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "progress", last: 50
+})
+const blockerMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "blocker", last: 10
+})
+```
+
 Output:
 ```
 [coordinator] Review Pipeline Status
@@ -45,9 +55,18 @@ Output:
 
   done=completed  >>>=running  o=pending  x=deleted
 
-[coordinator] Active Agents: <list from active_agents>
+[coordinator] Active Workers:
+  <task_id>  <role>  <milestone_phase>  <pct>%  "<summary>"  <time_ago>
+
+[coordinator] Blockers:
+  <task_id>  <role>  "<blocker_summary>"  <time_ago>
+  (omit section if no blockers)
+
 [coordinator] Ready to spawn: <subjects>
 [coordinator] Commands: 'resume' to advance | 'check' to refresh
+
+**CLI monitoring** (works while coordinator is blocked):
+maestro msg list -s "<session_id>" --type progress --last 10
 ```
 
 Then STOP.
@@ -99,31 +118,49 @@ state.tasks[taskId].status = 'in_progress'
 const agentId = spawn_agent({
   agent_type: "team_worker",
   task_name: taskId,  // e.g., "SCAN-001" — enables named targeting
-  items: [
-    { type: "text", text: `## Role Assignment
+  message: `## Role Assignment
 role: ${role}
 role_spec: ${skillRoot}/roles/${role}/role.md
 session: ${sessionFolder}
 session_id: ${sessionId}
 requirement: ${taskDescription}
-inner_loop: ${innerLoop}` },
+inner_loop: ${innerLoop}
 
-    { type: "text", text: `## Current Task
+## Current Task
 - Task ID: ${taskId}
 - Task: ${taskSubject}
 
 Read role_spec file to load Phase 2-4 domain instructions.
-Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).` }
-  ]
+Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).
+
+## Progress Milestones
+session_id: ${sessionId}
+Report progress via team_msg at natural phase boundaries.
+Report blockers immediately via team_msg type="blocker".
+Report completion via team_msg type="task_complete" after report_agent_job_result.`
 })
 
 // 3) Track agent
 state.active_agents[taskId] = { agentId, role, started_at: now }
 
 // 4) Wait for completion — use task_name for stable targeting (v4)
-const waitResult = wait_agent({ targets: [taskId], timeout_ms: 900000 })
+const waitResult = wait_agent({ timeout_ms: 900000 })
+
+// Drain progress from message bus
+const progressMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "progress", last: 100
+})
+for (const msg of (progressMsgs.result?.messages || [])) {
+  console.log(`[coordinator] trace: ${msg.summary}`)
+}
+
 if (waitResult.timed_out) {
+  const lastProgress = (progressMsgs.result?.messages || [])
+    .filter(m => m.data?.task_id === taskId).pop()
   state.tasks[taskId].status = 'timed_out'
+  state.tasks[taskId].error = lastProgress
+    ? `Timed out at ${lastProgress.data.phase} (${lastProgress.data.progress_pct}%)`
+    : 'Timed out with no progress reported'
   close_agent({ target: taskId })
   delete state.active_agents[taskId]
 } else {
@@ -161,12 +198,12 @@ When spawning workers in a later pipeline phase, send upstream results as supple
 // Example: Send scan results to running reviewer
 send_message({
   target: "<running-agent-task-name>",
-  items: [{ type: "text", text: `## Supplementary Context\n${upstreamFindings}` }]
+  message: `## Supplementary Context\n${upstreamFindings}`
 })
 // Note: send_message queues info without interrupting the agent's current work
 ```
 
-Use `send_message` (not `assign_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
+Use `send_message` (not `followup_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
 
 ## handleComplete
 

package/.codex/skills/team-review/roles/coordinator/role.md

@@ -6,7 +6,7 @@ Orchestrate team-review: parse target -> detect mode -> dispatch task chain -> m
 
 **You are a dispatcher, not a doer.** Your ONLY outputs are:
 - Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `followup_task` calls
 - Status reports to the user / `request_user_input` prompts
 
 **FORBIDDEN** (even if the task seems trivial):
@@ -36,7 +36,7 @@ WRONG: Edit/Write on project source files            — worker work
 - Maintain session state (tasks.json)
 - Execute completion action when pipeline finishes
 - **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `send_message` for supplementary context (non-interrupting) and `followup_task` for triggering new work
 - Use `list_agents` for session resume health checks and cleanup verification
 
 ### MUST NOT
@@ -157,11 +157,11 @@ Delegate to @commands/monitor.md#handleSpawnNext:
 
 ### Message Semantics
 - **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
-- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+- **followup_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
 
 ### Agent Lifecycle Management
 - **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
-- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, followup_task, and close_agent calls.
 
 ## Error Handling
 

package/.codex/skills/team-tech-debt/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-tech-debt
 description: Unified team skill for tech debt identification and remediation. Scans codebase for tech debt, assesses severity, plans and executes fixes with validation. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team tech debt".
-allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), assign_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*), mcp__maestro-tools__read_file(*), mcp__maestro-tools__write_file(*), mcp__maestro-tools__edit_file(*), mcp__maestro-tools__team_msg(*)
+allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ace-tool__search_context(*), mcp__maestro-tools__read_file(*), mcp__maestro-tools__write_file(*), mcp__maestro-tools__edit_file(*), mcp__maestro-tools__team_msg(*)
 ---
 
 # Team Tech Debt
@@ -55,7 +55,7 @@ Before calling ANY tool, apply this check:
 
 | Tool Call | Verdict | Reason |
 |-----------|---------|--------|
-| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `assign_task` | ALLOWED | Orchestration |
+| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `followup_task` | ALLOWED | Orchestration |
 | `list_agents` | ALLOWED | Agent health check |
 | `request_user_input` | ALLOWED | User interaction |
 | `mcp__maestro-tools__team_msg` | ALLOWED | Message bus |
@@ -88,9 +88,8 @@ 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
+  fork_turns: "none",
+  message: `## Role Assignment
 role: <role>
 role_spec: <skill_root>/roles/<role>/role.md
 session: <session-folder>
@@ -98,21 +97,20 @@ 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.` },
+Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
 
-    { type: "text", text: `## Task Context
+## Task Context
 task_id: <task-id>
 title: <task-title>
 description: <task-description>
-pipeline_phase: <pipeline-phase>` },
+pipeline_phase: <pipeline-phase>
 
-    { type: "text", text: `## Upstream Context
-<prev_context>` }
-  ]
+## Upstream Context
+<prev_context>`
 })
 ```
 
-After spawning, use `wait_agent({ targets: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
+After spawning, use `wait_agent({ timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
 
 
 ### Model Selection Guide
@@ -173,7 +171,7 @@ Scanner discoveries flow through the pipeline — each stage narrows and refines
 | Intent | API | Example |
 |--------|-----|---------|
 | Queue supplementary info (don't interrupt) | `send_message` | Send scan findings to running assessor |
-| Assign fix from remediation plan | `assign_task` | Assign TDFIX task from planner output |
+| Assign fix from remediation plan | `followup_task` | Assign TDFIX task from planner output |
 | Check running agents | `list_agents` | Verify agent health during resume |
 
 ### Agent Health Check
@@ -190,8 +188,8 @@ const running = list_agents({})
 ### Named Agent Targeting
 
 Workers are spawned with `task_name: "<task-id>"` enabling direct addressing:
-- `send_message({ target: "TDSCAN-001", items: [...] })` -- send additional scan scope to scanner
-- `assign_task({ target: "TDFIX-001", items: [...] })` -- assign fix task from planner output
+- `send_message({ target: "TDSCAN-001", message: "..." })` -- send additional scan scope to scanner
+- `followup_task({ target: "TDFIX-001", message: "..." })` -- assign fix task from planner output
 - `close_agent({ target: "TDVAL-001" })` -- cleanup after validation
 
 ## Error Handling

package/.codex/skills/team-tech-debt/roles/coordinator/commands/monitor.md

@@ -26,6 +26,16 @@ Read-only status report from tasks.json, then STOP.
 1. Read tasks.json
 2. Count tasks by status (pending, in_progress, completed, failed)
 
+```javascript
+// Read progress and blocker messages from message bus
+const progressMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "progress", last: 50
+})
+const blockerMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "blocker", last: 10
+})
+```
+
 ```
 Pipeline Status (<mode>):
   [DONE]  TDSCAN-001  (scanner)   -> scan complete
@@ -34,9 +44,19 @@ Pipeline Status (<mode>):
   [WAIT]  TDFIX-001   (executor)  -> blocked by TDPLAN-001
   [WAIT]  TDVAL-001   (validator) -> blocked by TDFIX-001
 
+[coordinator] Active Workers:
+  <task_id>  <role>  <milestone_phase>  <pct>%  "<summary>"  <time_ago>
+
+[coordinator] Blockers:
+  <task_id>  <role>  "<blocker_summary>"  <time_ago>
+  (omit section if no blockers)
+
 GC Rounds: 0/3
 Session: <session-id>
 Commands: 'resume' to advance | 'check' to refresh
+
+**CLI monitoring** (works while coordinator is blocked):
+maestro msg list -s "<session_id>" --type progress --last 10
 ```
 
 Output status -- do NOT advance pipeline.
@@ -83,26 +103,31 @@ state.tasks[taskId].status = 'in_progress'
 const agentId = spawn_agent({
   agent_type: "team_worker",
   task_name: taskId,  // e.g., "TDSCAN-001" — enables named targeting
-  items: [
-    { type: "text", text: `## Role Assignment
+  message: `## Role Assignment
 role: ${task.role}
 role_spec: ${skillRoot}/roles/${task.role}/role.md
 session: ${sessionFolder}
 session_id: ${sessionId}
 team_name: tech-debt
 requirement: ${task.description}
-inner_loop: ${task.role === 'executor'}` },
+inner_loop: ${task.role === 'executor'}
 
-    { type: "text", text: `Read role_spec file (${skillRoot}/roles/${task.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).` },
+Read role_spec file (${skillRoot}/roles/${task.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).
 
-    { type: "text", text: `## Task Context
+## Task Context
 task_id: ${taskId}
 title: ${task.title}
-description: ${task.description}` },
+description: ${task.description}
+
+## Upstream Context
+${prevContext}
 
-    { type: "text", text: `## Upstream Context\n${prevContext}` }
-  ]
+## Progress Milestones
+session_id: ${sessionId}
+Report progress via team_msg at natural phase boundaries.
+Report blockers immediately via team_msg type="blocker".
+Report completion via team_msg type="task_complete" after report_agent_job_result.`
 })
 
 // 3) Track agent
@@ -125,10 +150,24 @@ After spawning all ready tasks:
 ```javascript
 // 4) Batch wait — use task_name for stable targeting (v4)
 const taskNames = Object.keys(state.active_agents)
-const waitResult = wait_agent({ targets: taskNames, timeout_ms: 900000 })
+const waitResult = wait_agent({ timeout_ms: 900000 })
+
+// Drain progress from message bus
+const progressMsgs = mcp__maestro-tools__team_msg({
+  operation: "list", session_id: sessionId, type: "progress", last: 100
+})
+for (const msg of (progressMsgs.result?.messages || [])) {
+  console.log(`[coordinator] trace: ${msg.summary}`)
+}
+
 if (waitResult.timed_out) {
   for (const taskId of taskNames) {
+    const lastProgress = (progressMsgs.result?.messages || [])
+      .filter(m => m.data?.task_id === taskId).pop()
     state.tasks[taskId].status = 'timed_out'
+    state.tasks[taskId].error = lastProgress
+      ? `Timed out at ${lastProgress.data.phase} (${lastProgress.data.progress_pct}%)`
+      : 'Timed out with no progress reported'
     close_agent({ target: taskId })
     delete state.active_agents[taskId]
   }
@@ -214,12 +253,12 @@ When spawning workers in a later pipeline phase, send upstream results as supple
 // Example: Send scan results to running assessor
 send_message({
   target: "<running-agent-task-name>",
-  items: [{ type: "text", text: `## Supplementary Context\n${upstreamFindings}` }]
+  message: `## Supplementary Context\n${upstreamFindings}`
 })
 // Note: send_message queues info without interrupting the agent's current work
 ```
 
-Use `send_message` (not `assign_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
+Use `send_message` (not `followup_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
 
 ### Persist and Loop
 

package/.codex/skills/team-tech-debt/roles/coordinator/role.md

@@ -6,7 +6,7 @@
 
 **You are a dispatcher, not a doer.** Your ONLY outputs are:
 - Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `followup_task` calls
 - Status reports to the user / `request_user_input` prompts
 
 **FORBIDDEN** (even if the task seems trivial):
@@ -33,7 +33,7 @@ WRONG: Edit/Write on project source files            — worker work
 - Monitor worker progress via spawn_agent/wait_agent and route messages
 - Maintain session state persistence (tasks.json)
 - **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `send_message` for supplementary context (non-interrupting) and `followup_task` for triggering new work
 - Use `list_agents` for session resume health checks and cleanup verification
 
 ### MUST NOT
@@ -153,11 +153,11 @@ Delegate to @commands/monitor.md#handleSpawnNext:
 
 ### Message Semantics
 - **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
-- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+- **followup_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
 
 ### Agent Lifecycle Management
 - **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
-- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, followup_task, and close_agent calls.
 
 ## Error Handling
 

package/.codex/skills/team-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-testing
 description: Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".
-allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), assign_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*)
+allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__maestro-tools__team_msg(*)
 ---
 
 # Team Testing
@@ -54,7 +54,7 @@ Before calling ANY tool, apply this check:
 
 | Tool Call | Verdict | Reason |
 |-----------|---------|--------|
-| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `assign_task` | ALLOWED | Orchestration |
+| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `followup_task` | ALLOWED | Orchestration |
 | `list_agents` | ALLOWED | Agent health check |
 | `request_user_input` | ALLOWED | User interaction |
 | `mcp__maestro-tools__team_msg` | ALLOWED | Message bus |
@@ -87,9 +87,8 @@ 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
+  fork_turns: "none",
+  message: `## Role Assignment
 role: <role>
 role_spec: <skill_root>/roles/<role>/role.md
 session: <session-folder>
@@ -97,21 +96,20 @@ 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.` },
+Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
 
-    { type: "text", text: `## Task Context
+## Task Context
 task_id: <task-id>
 title: <task-title>
 description: <task-description>
-pipeline_phase: <pipeline-phase>` },
+pipeline_phase: <pipeline-phase>
 
-    { type: "text", text: `## Upstream Context
-<prev_context>` }
-  ]
+## Upstream Context
+<prev_context>`
 })
 ```
 
-After spawning, use `wait_agent({ targets: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
+After spawning, use `wait_agent({ timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
 
 
 ### Model Selection Guide
@@ -128,10 +126,10 @@ 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,
+  fork_turns: "none",
   model: "<model-override>",
   reasoning_effort: "<effort-level>",
-  items: [...]
+  message: "..."
 })
 ```
 
@@ -151,7 +149,7 @@ spawn_agent({
 | Intent | API | Example |
 |--------|-----|---------|
 | Send strategy to running generators | `send_message` | Queue test strategy findings to TESTGEN-* workers |
-| Not used in this skill | `assign_task` | No resident agents -- all workers are one-shot |
+| Not used in this skill | `followup_task` | No resident agents -- all workers are one-shot |
 | Check running agents | `list_agents` | Verify parallel generator/executor health |
 
 ### Parallel Test Generation
@@ -164,7 +162,7 @@ const genNames = ["TESTGEN-001", "TESTGEN-002"]
 for (const name of genNames) {
   spawn_agent({ agent_type: "team_worker", task_name: name, ... })
 }
-wait_agent({ targets: genNames, timeout_ms: 900000 })
+wait_agent({ timeout_ms: 900000 })
 ```
 
 ### GC Loop Coordination
@@ -185,7 +183,7 @@ const running = list_agents({})
 ### Named Agent Targeting
 
 Workers are spawned with `task_name: "<task-id>"` enabling direct addressing:
-- `send_message({ target: "TESTGEN-001", items: [...] })` -- queue strategy context to running generator
+- `send_message({ target: "TESTGEN-001", message: "..." })` -- queue strategy context to running generator
 - `close_agent({ target: "TESTRUN-001" })` -- cleanup by name after wait_agent returns
 
 ## Completion Action