go
/go -- Goal-Driven Entry Point
The single entry point to the entire Conductor system.
Just state your goal. The system handles everything else.
Usage
/go <your goal>
Examples
/go Add Stripe payment integration
/go Fix the login bug where users get logged out
/go Build a dashboard with analytics
/go Refactor the asset generation to use caching
What Happens
When you invoke /go, follow this process:
1. Goal Analysis
Parse the user's goal from $ARGUMENTS:
- Identify the type (feature, bugfix, refactor, etc.)
- Estimate complexity
- Extract key requirements
2. Track Detection
Check conductor/tracks.md for matching existing tracks:
- If match found: Resume that track from its current state
- If no match: Create a new track
3. For New Tracks
- Create track directory:
conductor/tracks/{goal-slug}_{date}/ - Generate
spec.mdfrom the goal - Generate
plan.mdwith DAG - Create
metadata.jsonwith v3 schema AND setsuperpower_enhanced: true(new tracks use superpowers by default)
Example metadata.json:
{
"version": 3,
"track_id": "goal-slug_20260213",
"type": "feature",
"status": "new",
"superpower_enhanced": true,
"loop_state": {
"current_step": "NOT_STARTED",
"step_status": "NOT_STARTED"
}
}
4. Run the Evaluate-Loop
Invoke the conductor-orchestrator agent:
Use the conductor-orchestrator agent to run the evaluate-loop for this track.
The orchestrator will:
- Detect current step from metadata
- Check
superpower_enhancedflag to determine which agents to use:- If true (new tracks): Dispatch superpowers (orchestrator-supaconductor:writing-plans, orchestrator-supaconductor:executing-plans, orchestrator-supaconductor:systematic-debugging)
- If false/missing (legacy): Dispatch legacy loop agents (loop-planner, loop-executor, loop-fixer)
- Monitor progress and handle failures
- Complete the track or escalate if blocked
Decision Resolution
Behavior depends on conductor/config.json → "mode":
"agentic"(default) — Fully autonomous. Never stops to ask the user. All decisions resolved by agents, leads, and board."human-in-the-loop"— Pauses at decision points (ambiguity, blockers, fix limits, high-impact decisions) to ask the user.
See conductor/config.json for current mode. Edit to switch.
Resume Existing Work
/go # Continues the active track
/go continue # Same as above
More from ibrahim-3d/conductor-orchestrator-superpowers
board-of-directors
Simulate a 5-member expert board deliberation for major decisions. Use when evaluating plans, architecture choices, feature designs, or any decision requiring multi-perspective expert analysis. Triggers: 'board review', 'get expert opinions', 'board meeting', 'director evaluation', 'consensus review'.
9conductor-orchestrator
Master coordinator for the Evaluate-Loop workflow v3. Supports GOAL-DRIVEN entry, PARALLEL execution via worker agents, BOARD OF DIRECTORS deliberation, and message bus coordination. Dispatches specialized workers dynamically, monitors via message bus, aggregates results. Uses metadata.json v3 for parallel state tracking. Use when: '/go <goal>', '/conductor implement', 'start track', 'run the loop', 'orchestrate', 'automate track'.
8eval-business-logic
Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user journey completeness. Dispatched by loop-execution-evaluator when track type is 'business-logic', 'generator', or 'core-feature'. Triggered by: 'evaluate logic', 'test business rules', 'verify business rules', 'check feature'.
8executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
7eval-integration
Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched by loop-execution-evaluator when track type is 'integration', 'auth', 'payments', or 'api'. Triggered by: 'evaluate integration', 'test auth flow', 'check API', 'verify payments'.
7agent-factory
Creates specialized worker agents dynamically from templates. Use when orchestrator needs to spawn task-specific workers for parallel execution. Handles agent lifecycle: create -> execute -> cleanup.
7