Menú
The single entry point to the Conductor system - state your goal and everything is handled automatically
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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'.
File-based message queue for inter-agent coordination. Used by workers AND board directors to communicate. Provides: progress updates, task completion signals, file locking, board deliberation. Core infrastructure for parallel execution.
Loads relevant patterns and known errors before track planning. Searches conductor/knowledge/ for solutions we've used before and errors we've encountered. Injects findings into the planner prompt to prevent reinventing solutions and repeating mistakes. Triggered automatically by orchestrator before PLAN step.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks. Enforces the Evaluate-Loop workflow.
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.
| name | go |
| description | The single entry point to the Conductor system - state your goal and everything is handled automatically |
The single entry point to the entire Conductor system.
Just state your goal. The system handles everything else.
/go <your goal>
/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
When you invoke /go, follow this process:
Parse the user's goal from $ARGUMENTS:
Check conductor/tracks.md for matching existing tracks:
conductor/tracks/{goal-slug}_{date}/spec.md from the goalplan.md with DAGmetadata.json with v3 schema AND set superpower_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"
}
}
Invoke the conductor-orchestrator agent:
Use the conductor-orchestrator agent to run the evaluate-loop for this track.
The orchestrator will:
superpower_enhanced flag to determine which agents to use:
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.
/go # Continues the active track
/go continue # Same as above