From orchestrator-supaconductor
Implements tasks from verified plan.md sequentially: writes code, verifies with TDD where applicable, updates plan progress, commits at checkpoints. For structured project execution.
npx claudepluginhub ibrahim-3d/orchestrator-supaconductor --plugin orchestrator-supaconductorThis skill uses the workspace's default tool permissions.
Implements the tasks defined in a verified `plan.md`. This agent writes code, creates files, and updates plan.md after every completed task.
Executes tasks from PLAN.md sequentially with human oversight, handling task splitting, clarifying questions, tests, and learning persistence. Useful for deliberate progress on planned work.
Executes implementation plans from plan.md files via Superpower Loop phases: task creation, batch execution with verification, git commits. Use after plan ready or on 'execute the plan'.
Executes written implementation plans: loads/reviews file, runs tasks autonomously (agentic mode) or in batches with pauses (human-in-loop), verifies, reports progress, completes branch.
Share bugs, ideas, or general feedback.
Implements the tasks defined in a verified plan.md. This agent writes code, creates files, and updates plan.md after every completed task.
Before writing any code:
plan.md — find first [ ] task (skip all [x] tasks)1. Mark task [~] in plan.md (in progress)
2. read_file acceptance criteria
3. Implement the task
4. Verify acceptance criteria met
5. Update plan.md immediately:
- Mark [x]
- Add commit SHA
- Add summary of what was done
6. Commit code changes
7. Move to next [ ] task
- [x] Task 3: Build signup form component <!-- abc1234 -->
- Created src/components/auth/signup-form.tsx
- Added email validation (regex), password min 8 chars
- Integrated with authApi.signUp() from mock API client
- Acceptance: ✅ Form renders, validates, submits
For tasks involving business logic, follow TDD from the tdd-implementation skill:
RED → write_file failing test for the task's acceptance criteria
GREEN → write_file minimal code to pass
REFACTOR → Clean up while tests stay green
Apply TDD to:
Skip TDD for:
Commit at these checkpoints:
feat([scope]): [what was done]While executing, if you discover work not in the plan:
## Discovered Work
- [ ] [Description of discovered work]
- Reason: [Why this is needed]
- Recommendation: [Add to current track / Create new track]
Add to plan.md under "Discovered Work" section. Do NOT silently implement it.
While executing, if a task makes any of these changes, flag it for Step 5.5 (Business Doc Sync):
Add a note in the execution summary:
**Business Doc Sync Required**: Yes/No
**Reason**: [e.g., "Added premium tier with Pro model"]
**Affected Docs**: [list from business-docs-sync skill registry]
See ${CLAUDE_PLUGIN_ROOT}/skills/business-docs-sync/SKILL.md for the full sync registry and protocol.
If a task cannot be completed:
[!] with explanationAfter completing all tasks (or hitting a blocker):
## Execution Summary
**Track**: [track-id]
**Tasks Completed**: [X]/[Y]
**Tasks Blocked**: [count, if any]
**Commits**: [list of commit SHAs]
**Discovered Work**: [count, if any]
**Ready for**: Step 4 (Evaluate Execution) → hand off to loop-execution-evaluator
The executor MUST update the track's metadata.json at key points:
{
"loop_state": {
"current_step": "EXECUTE",
"step_status": "IN_PROGRESS",
"step_started_at": "[ISO timestamp]",
"checkpoints": {
"EXECUTE": {
"status": "IN_PROGRESS",
"started_at": "[ISO timestamp]",
"agent": "loop-executor",
"tasks_completed": 0,
"tasks_total": "[count from plan.md]",
"commits": []
}
}
}
}
{
"loop_state": {
"checkpoints": {
"EXECUTE": {
"status": "IN_PROGRESS",
"tasks_completed": 3,
"tasks_total": 10,
"last_task": "Task 1.3",
"last_commit": "abc1234",
"commits": [
{ "sha": "abc1234", "message": "feat: add form", "task": "Task 1.3" }
]
}
}
}
}
{
"loop_state": {
"current_step": "EVALUATE_EXECUTION",
"step_status": "NOT_STARTED",
"checkpoints": {
"EXECUTE": {
"status": "PASSED",
"completed_at": "[ISO timestamp]",
"tasks_completed": 10,
"tasks_total": 10,
"last_task": "Task 3.2",
"last_commit": "def5678",
"commits": [...]
},
"EVALUATE_EXECUTION": {
"status": "NOT_STARTED"
}
}
}
}
metadata.json at starttasks_completed, last_task, last_commit after EACH taskcurrent_step to EVALUATE_EXECUTIONmetadata.jsonIf executor is restarted mid-execution:
metadata.json.checkpoints.EXECUTE.last_taskplan.md[ ] task after the last completed one[x] tasksAfter execution completes, the Conductor dispatches the loop-execution-evaluator to verify everything was built correctly.