Workflow Task Orchestration

Planning Gate

• Reuse the plan-first gate from workflow-foundation before any delegation.
• Resolve and read the latest active revision first; if it is missing, create revision 1 with the same structure used by /spwnr:plan.
• Keep goal, success criteria, scope boundaries, constraints, open risks, approval condition, current-run execution confirmation, plan artifact path, and executable Execution Units visible in TodoWrite.
• Treat only the latest active revision as executable. Superseded revisions and their tasks are audit-only.
• If the current run has not yet received Execute current plan, stay in the execution review loop instead of delegating.

Approved Execution Spec

Before any TaskCreate:

1. Validate that the latest active revision contains executable Execution Units, Environment And Preconditions, Execution Strategy Recommendation, Agent Capability Requirements, and Failure And Escalation Rules.
2. Produce a short plan summary, a normalized registry lookup brief, and one concise per-unit coverage brief for each execution unit.
3. Resolve the candidate pool from the local registry. If multiple units exist, use per-unit coverage to prove the lineup that covers every execution unit.
4. Read the selected mode and execution pattern from Execution Strategy Recommendation instead of inventing them at execution time.
5. If the selected mode is pipeline, validate that the pattern name, ordered stages, and stage handoffs are present.
6. If the selected mode is team, validate whether the plan expects one shared queue or multiple pipelines launched in parallel.
7. In team mode, default the task graph toward parallel tasks with disjoint Files: ownership. If the plan needs shared-file collaboration, validate that the exception is explicit and that the plan defines worktree isolation or one concrete owner for that file.
8. If team is required but CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is unavailable, stop and say so explicitly instead of silently downgrading.
9. Append Approved Execution Spec to the active revision with Edit, including the selected mode, routing target, normalized registry lookup brief, and per-unit coverage summary.

Routing Decision

• Route to workflow-task-with-pipeline when the approved mode is pipeline.
• Route to workflow-task-with-team when the approved mode is team.
• pipeline must remain available without Claude team features.
• team may launch multiple bounded pipelines in parallel when the approved plan says so.
• team should not default to multiple parallel tasks editing the same file unless the approved plan explicitly marks that as an exception.
• Do not silently reroute a team plan into pipeline when team prerequisites fail.

Team Mode Subagent Obligations

Every subagent invoked in team mode must follow these two non-negotiable contracts. Include both contracts verbatim in every agent brief alongside the Failure Recovery Contract.

Progress Sync Contract

All progress of work must be synced with the team lead via SendMessage:

• On task start: send the accepted work package, assigned unit, and first planned step.
• After each meaningful step: send the completed step, its outcome, and the next planned step.
• On task completion: send a final status summary listing all completed steps and the resulting outputs or artefacts.
• On any block or scope question: send immediately as described in the Failure Recovery Contract below.

Every sync message must include these fields: unit, step, status (one of in_progress, step_done, complete, or blocked), summary, and next_step. When status is complete or blocked, set next_step to none; when status is in_progress or step_done, next_step must name the upcoming step.

Local Storage Contract

All work done must be stored locally before proceeding to the next step:

• After every meaningful step, invoke report_progress to commit and persist completed changes.
• Never accumulate multiple steps of uncommitted work; each step's output must be durable before the next step begins.
• If report_progress fails, treat it as a blocking incident: stop all work, report the failure to the team lead via SendMessage with status: blocked, and do not continue until the team lead explicitly sends a recovery signal (such as resume or retry) confirming that local storage is stable.

Failure Recovery Contract

Every selected agent brief must include the Team Mode Subagent Obligations above and this failure contract:

• if a permission denial, dependency gap, plan contradiction, or worktree failure appears, do not stop silently
• attempt one plan-consistent fallback when that fallback does not change scope
• if the issue remains, use TaskUpdate to mark the task blocked and explain why
• then use SendMessage to the lead with failed tool, reason, attempted fallback, impact, and recommended next step when the routed execution path is using a Claude team
• never mark the parent task complete while the issue is unresolved

When the run is pipeline, the controller must follow the same incident standard in the user-facing response and task updates.

Worker Readiness Required

If /spwnr:task cannot form a usable lineup, stop with these sections:

1. Plan Artifact
2. Readiness Gap
3. Missing Capabilities
4. Recovery Steps
5. Next Step

The recovery steps must list the missing capabilities or packages, tell the user to run /spwnr:workers, tell them to install or inject the missing agents, and say that execution should resume from the same active revision after readiness is restored.

Rules

• Do not delegate before the current run explicitly chooses Execute current plan.
• Do not mutate state from the planning phase of /spwnr:task.
• Do not keep executing against a superseded plan revision when a material re-plan has created a newer active revision.
• Do not skip the review stage.
• Do not let the reviewer invent new scope.
• Treat the plan file as the source of truth; later agents should not reconstruct it from chat alone.
• Treat the registry candidate pool and per-unit coverage plan as the source of truth for lineup selection.
• Tailor the output contract to the routed execution skill's job.
• In team mode, every subagent must satisfy both the Progress Sync Contract and the Local Storage Contract before proceeding to the next step; skipping either contract is not permitted.