/loop-execution-evaluator
The track ID to evaluate
> /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-execution-evaluator
Context preview
What this command does when you run it.
The track ID to evaluate
Command definition
loop-execution-evaluator.mdname: loop-execution-evaluator
description: "Verify implementation quality. Evaluate-Loop Step 4."
model: sonnet
arguments:
- name: track_id
description: "The track ID to evaluate"
required: true
user_invocable: true/loop-execution-evaluator — Evaluate Implementation
Evaluate-Loop Step 4: Verify the implementation meets quality standards.
Usage
/loop-execution-evaluator <track-id>
Your Task
You ARE the loop-execution-evaluator agent. Run quality checks based on track type.
Determine Track Type
Read `spec.md` for keywords:
- UI keywords → Apply UI/UX checks
- Feature keywords → Apply code quality checks
- Integration keywords → Apply integration checks
- Business logic keywords → Apply business logic checks
UI/UX Checks (8 Passes)
1. Design tokens used correctly 2. Visual consistency across screens 3. Layout structure (header, footer, container) 4. Responsive breakpoints work 5. Component states complete (hover, focus, disabled, loading) 6. Animations and transitions 7. Accessibility baseline (labels, alt text, focus) 8. Usability check (copy quality, no jargon)
Code Quality Checks (6 Passes)
1. `npm run build` passes 2. `npm run typecheck` passes (no `any` types) 3. Code patterns followed (naming, imports, DRY) 4. Error handling present 5. Dead code removed (no unused exports, console.logs) 6. Test coverage meets targets (70% overall, 90% business logic)
Integration Checks
- API contracts match expected schema
- Auth flows work correctly
- Data persists to database
- Error recovery handles failures
Business Logic Checks
- Product rules enforced correctly
- Edge cases handled
- State transitions are correct
Output
Append evaluation report to `plan.md`:
## Execution Evaluation Report
**Track**: {track_id}
**Date**: YYYY-MM-DD
| Evaluator | Status |
|-----------|--------|
| UI/UX | PASS |
| Code Quality | PASS |
| Integration | N/A |
| Business Logic | PASS |
### Verdict: PASSUpdate `metadata.json`:
- On PASS: `current_step = "COMPLETE"`, `step_status = "PASSED"`
- On FAIL: `current_step = "FIX"`, `step_status = "NOT_STARTED"`, increment `fix_cycle_count`
Fix Cycle Limit
If `fix_cycle_count >= 5`, mark track as `completed-with-warnings` instead of continuing. Log unresolved issues in metadata.
Message Bus
echo "PASS" > .message-bus/events/EXEC_EVAL_COMPLETE_{track_id}.event
# or
echo "FAIL" > .message-bus/events/EXEC_EVAL_COMPLETE_{track_id}.eventReference
Full agent instructions: `.claude/agents/loop-execution-evaluator.md`
Read more
name: loop-execution-evaluator
description: "Verify implementation quality. Evaluate-Loop Step 4."
model: sonnet
arguments:
- name: track_id
description: "The track ID to evaluate"
required: true
user_invocable: true/loop-execution-evaluator — Evaluate Implementation
Evaluate-Loop Step 4: Verify the implementation meets quality standards.
Usage
/loop-execution-evaluator <track-id>
Your Task
You ARE the loop-execution-evaluator agent. Run quality checks based on track type.
Determine Track Type
Read `spec.md` for keywords:
- UI keywords → Apply UI/UX checks
- Feature keywords → Apply code quality checks
- Integration keywords → Apply integration checks
- Business logic keywords → Apply business logic checks
UI/UX Checks (8 Passes)
1. Design tokens used correctly 2. Visual consistency across screens 3. Layout structure (header, footer, container) 4. Responsive breakpoints work 5. Component states complete (hover, focus, disabled, loading) 6. Animations and transitions 7. Accessibility baseline (labels, alt text, focus) 8. Usability check (copy quality, no jargon)
Code Quality Checks (6 Passes)
1. `npm run build` passes 2. `npm run typecheck` passes (no `any` types) 3. Code patterns followed (naming, imports, DRY) 4. Error handling present 5. Dead code removed (no unused exports, console.logs) 6. Test coverage meets targets (70% overall, 90% business logic)
Integration Checks
- API contracts match expected schema
- Auth flows work correctly
- Data persists to database
- Error recovery handles failures
Business Logic Checks
- Product rules enforced correctly
- Edge cases handled
- State transitions are correct
Output
Append evaluation report to `plan.md`:
## Execution Evaluation Report
**Track**: {track_id}
**Date**: YYYY-MM-DD
| Evaluator | Status |
|-----------|--------|
| UI/UX | PASS |
| Code Quality | PASS |
| Integration | N/A |
| Business Logic | PASS |
### Verdict: PASSUpdate `metadata.json`:
- On PASS: `current_step = "COMPLETE"`, `step_status = "PASSED"`
- On FAIL: `current_step = "FIX"`, `step_status = "NOT_STARTED"`, increment `fix_cycle_count`
Fix Cycle Limit
If `fix_cycle_count >= 5`, mark track as `completed-with-warnings` instead of continuing. Log unresolved issues in metadata.
Message Bus
echo "PASS" > .message-bus/events/EXEC_EVAL_COMPLETE_{track_id}.event
# or
echo "FAIL" > .message-bus/events/EXEC_EVAL_COMPLETE_{track_id}.eventReference
Full agent instructions: `.claude/agents/loop-execution-evaluator.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

