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/orchestrator-supaconductor
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
4loop-fixer
Evaluate-Loop Step 5: FIX. Use this agent when an evaluation (plan or execution) returns FAIL. Takes the evaluator's fix list, creates specific fix tasks in plan.md, executes the fixes, and triggers re-evaluation. Handles the loop-back mechanism of the Evaluate-Loop. Triggered by: evaluation FAIL verdict, 'fix issues', 'address evaluation failures'.
4using-supaconductor
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
3writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
3agent-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.
3context-loader
Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
3