From orchestrator-supaconductor
Evaluates track/phase completion: verifies deliverables, plan alignment, quality gates, tests, and docs; generates PASS/FAIL report. Optional track ID.
How this command is triggered — by the user, by Claude, or both
Slash command
/orchestrator-supaconductor:phase-reviewopusThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /orchestrator-supaconductor:phase-review Run the **Evaluate Execution** step of the Evaluate-Loop workflow. This is the mandatory quality gate before marking any track or phase complete. ## When to Use Run this command: - After finishing all tasks in a track/phase (Step 4 of the Evaluate-Loop) - Before marking anything as complete in `tracks.md` - When you want to verify alignment between plan and execution ## What It Does 1. Reads the current track's `spec.md` and `plan.md` 2. Runs the full post-execution evaluation checklist 3. Identifies misalignment between plan and execution 4. ...
Run the Evaluate Execution step of the Evaluate-Loop workflow. This is the mandatory quality gate before marking any track or phase complete.
Run this command:
tracks.mdspec.md and plan.md/orchestrator-supaconductor:phase-review
Or with a specific track:
/orchestrator-supaconductor:phase-review TRACK-001-feature-implementation
The command verifies all checks from the Evaluate-Loop:
spec.md are presentplan.md describedplan.md is fully updated with [x] markers and summariesworkflow.md checklistplan.md fully updated with task completion summariesThe command generates a completion report:
## Phase Completion Report
**Track**: [Track Name]
**Date**: [YYYY-MM-DD]
**Evaluation**: PASS | FAIL
### Deliverables
- [x] Deliverable 1 - src/components/auth/signup-form.tsx
- [x] Deliverable 2 - src/lib/api-client.ts
- [ ] Deliverable 3 - MISSING: src/hooks/useFeature.ts
### Alignment
- [x] All planned tasks executed
- [ ] DRIFT: Design system was rebuilt (not in plan)
### Quality Gates
- [x] Usability check (3 UI changes reviewed)
- [x] No console errors
- [x] Build successful
### Issues Found
1. [Issue description and severity]
### Verdict
PASS — Ready to mark complete
OR
FAIL — Fix required before completion
- Fix 1: [description]
- Fix 2: [description]
tracks.mdconductor/index.md current statusdocs: complete [TRACK-NAME] - evaluation passedplan.md/orchestrator-supaconductor:phase-review (loop back to Step 4)conductor/workflow.md — Evaluate-Loop Process (primary reference)CLAUDE.md — Mandatory Agent Rules/orchestrator-supaconductor:status — See current track status/orchestrator-supaconductor:implement — Execute track tasksnpx claudepluginhub ibrahim-3d/orchestrator-supaconductor --plugin orchestrator-supaconductor/fire-4-verifyVerifies specified phase completion using must-haves checklist and 70-point WARRIOR validation. Generates detailed report, optionally spawns reviewer, and routes to gap closure if needed. Supports --detailed, --quick, --report-only flags.
/implementExecutes TDD implementation workflow for selected or next incomplete track, resuming from plan.md progress markers. Supports [<track-name>] [--all] args.
/verifyVerifies project tests, acceptance criteria from files, or roadmap phases. Dispatches verifier agent to execute checks and report PASS/FAIL with evidence.
/flow-gate-checkOrchestrates multi-agent validation for SDLC phase gates like inception, security, or pre-deploy in a project directory, generating comprehensive readiness reports with optional guidance and interactive Q&A.