/task-worker
The specific task ID to execute (e.g., 1.1, 2.3)
> /plugin marketplace add Ibrahim-3d/orchestrator-supaconductor > /plugin install orchestrator-supaconductor@ibrahim-plugins
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/task-worker
Context preview
What this command does when you run it.
The specific task ID to execute (e.g., 1.1, 2.3)
Command definition
task-worker.mdname: task-worker
description: "Execute a single task from the plan. Used for parallel execution."
model: sonnet
arguments:
- name: track_id
description: "The track ID"
required: true
- name: task_id
description: "The specific task ID to execute (e.g., 1.1, 2.3)"
required: true
user_invocable: true/orchestrator-supaconductor:task-worker — Execute Single Task
Ephemeral worker for executing a single task. Used by parallel-dispatcher for concurrent execution.
Usage
/orchestrator-supaconductor:task-worker <track-id> <task-id>
Your Task
You ARE a task-worker agent. Execute ONLY the specified task.
1. **Register with message bus**:
# Update worker-status.json
2. **Read task from plan.md**: Find task matching `{task_id}`
3. **Acquire file locks** if modifying shared files:
- Check `.message-bus/locks.json`
- Add lock for files you'll modify
4. **Implement the task**:
- Read existing code first
- Follow project patterns
- Write tests if applicable
- Commit changes
5. **Post heartbeat** every 5 minutes (for long tasks)
6. **Release locks** after completion
7. **Post completion event**:
echo "{commit_sha}" > .message-bus/events/TASK_COMPLETE_{task_id}.event
# or on failure:
echo "{error_message}" > .message-bus/events/TASK_FAILED_{task_id}.eventCommit Format
feat(track-id): Task {task_id} - {task_name}
- {change 1}
- {change 2}
Worker: worker-{task_id}-{timestamp}
Co-Authored-By: Claude <noreply@anthropic.com>Update plan.md
Mark your task complete:
- [x] Task {task_id}: {name} <!-- {commit_sha} -->
- {summary of changes}Output
TASK COMPLETE: {task_id}
COMMIT: {sha}
FILES: {list of files modified}Reference
Full agent instructions: `.claude/agents/orchestrator-supaconductor:task-worker.md`
Read more
name: task-worker
description: "Execute a single task from the plan. Used for parallel execution."
model: sonnet
arguments:
- name: track_id
description: "The track ID"
required: true
- name: task_id
description: "The specific task ID to execute (e.g., 1.1, 2.3)"
required: true
user_invocable: true/orchestrator-supaconductor:task-worker — Execute Single Task
Ephemeral worker for executing a single task. Used by parallel-dispatcher for concurrent execution.
Usage
/orchestrator-supaconductor:task-worker <track-id> <task-id>
Your Task
You ARE a task-worker agent. Execute ONLY the specified task.
1. **Register with message bus**:
# Update worker-status.json
2. **Read task from plan.md**: Find task matching `{task_id}`
3. **Acquire file locks** if modifying shared files:
- Check `.message-bus/locks.json`
- Add lock for files you'll modify
4. **Implement the task**:
- Read existing code first
- Follow project patterns
- Write tests if applicable
- Commit changes
5. **Post heartbeat** every 5 minutes (for long tasks)
6. **Release locks** after completion
7. **Post completion event**:
echo "{commit_sha}" > .message-bus/events/TASK_COMPLETE_{task_id}.event
# or on failure:
echo "{error_message}" > .message-bus/events/TASK_FAILED_{task_id}.eventCommit Format
feat(track-id): Task {task_id} - {task_name}
- {change 1}
- {change 2}
Worker: worker-{task_id}-{timestamp}
Co-Authored-By: Claude <noreply@anthropic.com>Update plan.md
Mark your task complete:
- [x] Task {task_id}: {name} <!-- {commit_sha} -->
- {summary of changes}Output
TASK COMPLETE: {task_id}
COMMIT: {sha}
FILES: {list of files modified}Reference
Full agent instructions: `.claude/agents/orchestrator-supaconductor:task-worker.md`
Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills
Repo: Ibrahim-3d/orchestrator-supaconductor
Other commands on orchestrator-supaconductor.
- /board-meeting
The proposal, plan, or decision to deliberate on
Open command - /board-review
The proposal, plan, or decision to review
Open command - /brainstorm
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
Open command - /brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
Open command - /ceo
Your business question or topic to discuss
Open command - /close-track
Skip quality gate — use for abandoned or superseded tracks
Open command

