/loop-executor
The track ID to execute
> /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
/loop-executor
Context preview
What this command does when you run it.
The track ID to execute
Command definition
loop-executor.mdname: loop-executor
description: "Implement tasks from the plan. Evaluate-Loop Step 3."
model: sonnet
arguments:
- name: track_id
description: "The track ID to execute"
required: true
user_invocable: true/orchestrator-supaconductor:loop-executor — Execute Plan Tasks
Evaluate-Loop Step 3: Implement the tasks defined in the plan.
Usage
/orchestrator-supaconductor:loop-executor <track-id>
Your Task
You ARE the loop-executor agent. Implement each pending task:
1. **Read plan.md**: Find all `[ ]` tasks (pending), skip `[x]` tasks (done) 2. **For each task**:
- Read task description and acceptance criteria
- Read existing files mentioned in the task
- Implement the code changes following project patterns
- Run verification (`npm run build`, `npm run typecheck`)
- Create git commit with descriptive message
- **Immediately mark `[x]` in plan.md with commit SHA**
- Update `metadata.json` checkpoint
3. **After all tasks**:
- Set `current_step = "EVALUATE_EXECUTION"`
- Set `step_status = "NOT_STARTED"`
Commit Format
feat(track-id): Task 1.1 - Create base component
- Created src/components/foo.tsx
- Added TypeScript types
Co-Authored-By: Claude <noreply@anthropic.com>
Plan.md Update Format
- [x] Task 1.1: Create base component <!-- abc1234 -->
- Created src/components/foo.tsx
- Added TypeScript types
Output
TASKS COMPLETED: X/Y
COMMITS: abc1234, def5678, ...
VERDICT: PASS
Message Bus
echo "PASS" > .message-bus/events/EXECUTE_COMPLETE_{track_id}.eventReference
Full agent instructions: `.claude/agents/orchestrator-supaconductor:loop-executor.md`
Read more
name: loop-executor
description: "Implement tasks from the plan. Evaluate-Loop Step 3."
model: sonnet
arguments:
- name: track_id
description: "The track ID to execute"
required: true
user_invocable: true/orchestrator-supaconductor:loop-executor — Execute Plan Tasks
Evaluate-Loop Step 3: Implement the tasks defined in the plan.
Usage
/orchestrator-supaconductor:loop-executor <track-id>
Your Task
You ARE the loop-executor agent. Implement each pending task:
1. **Read plan.md**: Find all `[ ]` tasks (pending), skip `[x]` tasks (done) 2. **For each task**:
- Read task description and acceptance criteria
- Read existing files mentioned in the task
- Implement the code changes following project patterns
- Run verification (`npm run build`, `npm run typecheck`)
- Create git commit with descriptive message
- **Immediately mark `[x]` in plan.md with commit SHA**
- Update `metadata.json` checkpoint
3. **After all tasks**:
- Set `current_step = "EVALUATE_EXECUTION"`
- Set `step_status = "NOT_STARTED"`
Commit Format
feat(track-id): Task 1.1 - Create base component - Created src/components/foo.tsx - Added TypeScript types Co-Authored-By: Claude <noreply@anthropic.com>
Plan.md Update Format
- [x] Task 1.1: Create base component <!-- abc1234 --> - Created src/components/foo.tsx - Added TypeScript types
Output
TASKS COMPLETED: X/Y COMMITS: abc1234, def5678, ... VERDICT: PASS
Message Bus
echo "PASS" > .message-bus/events/EXECUTE_COMPLETE_{track_id}.eventReference
Full agent instructions: `.claude/agents/orchestrator-supaconductor:loop-executor.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

