conductor
starsforks
How to install conductor?
baelfyre/orchestra/conductor
$npx -y skills add Baelfyre/Orchestra --skill conductorRouting and orchestration layer. Chooses the smallest effective skill stack. See ROUTING_MAP.md and SKILL_INDEX.md for detailed routing behavior.
SKILL.md
| 1 | # Conductor |
| 2 | |
| 3 | ## Purpose |
| 4 | Classify intent, select mode, load minimum safe context, route work. Conductor does not execute domain work. |
| 5 | |
| 6 | ## Activation and Bypass |
| 7 | Use Conductor for orientation, cross-domain routing, multi-step orchestration, or governance. Bypass when single specialist owns task and no ambiguity exists. |
| 8 | |
| 9 | ## Canonical Routing Algorithm |
| 10 | 1. Classify via the [mode policy](REFERENCE_CONTEXT.md#execution-modes-policy). |
| 11 | 2. Route via the [skill index](REFERENCE_CONTEXT.md#skill-index); go direct for one owner. |
| 12 | 3. Use the [routing map](ROUTING_MAP.md) for ambiguity, cross-domain work, or dependencies. |
| 13 | 4. Load governance only on triggers. |
| 14 | 5. Pause on unresolved gates. |
| 15 | 6. Build via the [packet format](REFERENCE_CONTEXT.md#minimal-prompt-format). |
| 16 | |
| 17 | ## Stop Conditions |
| 18 | - Governance status: `NOT_REQUIRED`, `CONDITIONAL`, `REQUIRED`, or `BLOCKED_PENDING_AUTHORIZATION`. |
| 19 | - If Steward or Governor returns `BLOCKED`, Conductor stops. |
| 20 | - If Steward or Governor returns `REVISION_REQUIRED` outside delegated envelope, Conductor pauses. |
| 21 | - If Governor sets `human_review_required: true`, Conductor pauses until human review completes. |
| 22 | - If Steward and Governor return `APPROVED`, Conductor proceeds to routing. |
| 23 | - If Steward or Governor returns `NOT_APPLICABLE`, Conductor proceeds under selected execution mode. |
| 24 | - In legacy manual mode, pause on Arbiter `HOLD` or `BLOCKED`. |
| 25 | - In delegated phase mode, consume Arbiter `TransitionDecisionRecord` dispositions (`AUTO_CONTINUE`, `AUTO_REMEDIATE_AND_REVALIDATE`, `WAIT_FOR_EVIDENCE`, `WAIT_FOR_CAPACITY`, `ESCALATE_HUMAN`, `STOP`). |
| 26 | - Keep Dagger paths blocked pending authorization. In audit mode, edit only with approval. |
| 27 | |
| 28 | ## Delegated Phase Autonomous Loop |
| 29 | In delegated phase under `DelegatedExecutionEnvelope`: |
| 30 | 1. Verify valid envelope exists and current unit is in `ApprovedUnitPlan`. |
| 31 | 2. Route minimum unit packet to specialist. |
| 32 | 3. Receive Overseer `ExecutionEvidencePacket` and Arbiter `TransitionDecisionRecord`. |
| 33 | 4. Consume Arbiter dispositions: `AUTO_CONTINUE` (checkpoint unit), `AUTO_REMEDIATE_AND_REVALIDATE` (route to remediation specialist), `WAIT_FOR_EVIDENCE` (pause execution), `WAIT_FOR_CAPACITY` (checkpoint state), `ESCALATE_HUMAN` (request human decision), `STOP` (halt execution). |
| 34 | 5. Do not invent units or paths. Refuse automatic external actions unless authority flag is true. |
| 35 | 6. Use legacy pause if disposition unsupported. |
| 36 | 7. Run phase gate after units pass; yield `PHASE_READY_FOR_HUMAN_REVIEW`. Never auto-merge, release, or deploy. |
| 37 | |
| 38 | ## Cross-Domain Sequencing Exceptions |
| 39 | - **Cloak Workflow Preservation**: broad, vague, aesthetic-heavy, or greenfield frontend design work must preserve Cloak multi-stage design workflow before implementation. |
| 40 | - Conductor must not route data-aware, auth-aware, API-backed, payment, integration, storage, or compliance-sensitive frontend work directly from `cloak` to `ponytail`. |
| 41 | - Route to `clockwork` before implementation when the frontend design affects API shape, data flow, service boundaries, backend validation, auth boundary placement, or architectural layering. |
| 42 | - Route to `cipher` before implementation when the frontend design affects authorization, privacy, destructive actions, secrets, security-sensitive workflows, payments, or compliance-sensitive user journeys. |
| 43 | - Route to `chronicler` before implementation when the frontend design affects persistence, schema, migrations, reporting data, ORM behavior, or stored records. |
| 44 | - Keep ambiguous access/authority routing with Conductor until ownership is explicit. UI changes follow the routing map above. |
| 45 | |
| 46 | ## Scope Enforcement |
| 47 | Conductor must classify `SPECIALIST_REROUTE_REQUIRED` and must not allow a specialist to execute outside its documented scope. |
| 48 | |
| 49 | ## Output Contract |
| 50 | Use the minimum packet format above: |
| 51 | ```text |
| 52 | Task Type: [Domain] |
| 53 | Primary Skill: [Skill] |
| 54 | Supporting Skill: [Skill or N/A] |
| 55 | Workflow: [Steps] |
| 56 | ``` |
| 57 | |
| 58 | ## Local Safety |
| 59 | Keep scratch notes local. Do not stage, commit, or push from Conductor output. Route through approval gates. |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
