How do I install the Conductor Router skill?

Run npx skillmds@latest add scoobydrew83/conductor-router in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Conductor Router safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Conductor Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Conductor Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Conductor Router?

scoobydrew83 (@scoobydrew83) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Conductor Router by scoobydrew83 — Agent Skill

Name: Conductor Router
Author: scoobydrew83

Conductor Router

Route one Conductor queue item through Orient, Frame, Authorize, Execute, Verify, Review, and Learn without doing the item itself. Use when an agent needs to determine the next legal lifecycle phase, resume a loop, reconcile a queue state with verdicts, or decide whether to escalate. It enforces loop policy, explicit human gates, evidence requirements, and the three-failure stop. Do NOT use it to bypass a human decision or to implement a queue item.

scoobydrew83 Updated Sep 17, 2026

File contents

Conductor Router

Read the project state and return one legal transition only. The authoritative order is FEATURES.json, .harness/loop-policy.json, LOOP_QUEUE.md, current verdict evidence, then narrative context. Use next-step/scripts/route_next.py for the deterministic queue read.

When a human or verifier authorizes the transition, use scripts/transition.py <repo> <item-id> <state>. It persists only a legal queue transition and redacted evidence. Leaving a human-gated state requires --human-decision; VERIFYING → DONE requires a feature ID and reproducible --check COMMAND|EXPECTED|ACTUAL evidence. The runner never performs the work item, sends outreach, deploys, or merges.

ORIENTING: choose PENDING only when criteria and policy exist; otherwise choose AWAITING_HUMAN with the missing decision.
PENDING / IN_PROGRESS: dispatch one bounded item to the builder.
VERIFYING: dispatch an independent verifier. PASS becomes DONE; a FAIL returns only listed fixes to IN_PROGRESS; a third failure becomes BLOCKED_HUMAN.
AWAITING_HUMAN / BLOCKED_HUMAN: do not dispatch. Present Decision needed and the evidence that makes it necessary.
DONE: record the evidence and offer the next pending item or a clean stop.

The router never edits acceptance criteria, approves assumptions, merges, or changes policy. It records only the chosen transition and its reason.

Next steps: When state or policy is malformed, suggest conductor-doctor. When the person does not know the work's next action, suggest next-step. When a material assumption blocks progress, suggest assumption-grill.

---name: conductor-routerdescription: Route one Conductor queue item through Orient, Frame, Authorize, Execute, Verify, Review, and Learn without doing the item itself. Use when an agent needs to determine the next legal lifecycle phase, resume a loop, reconcile a queue state with verdicts, or decide whether to escalate. It enforces loop policy, explicit human gates, evidence requirements, and the three-failure stop. Do NOT use it to bypass a human decision or to implement a queue item.---# Conductor RouterRead the project state and return one legal transition only. The authoritativeorder is `FEATURES.json`, `.harness/loop-policy.json`, `LOOP_QUEUE.md`, currentverdict evidence, then narrative context. Use `next-step/scripts/route_next.py`for the deterministic queue read.When a human or verifier authorizes the transition, use`scripts/transition.py <repo> <item-id> <state>`. It persists only a legalqueue transition and redacted evidence. Leaving a human-gated state requires`--human-decision`; `VERIFYING → DONE` requires a feature ID and reproducible`--check COMMAND|EXPECTED|ACTUAL` evidence. The runner never performs the workitem, sends outreach, deploys, or merges.- **ORIENTING:** choose `PENDING` only when criteria and policy exist; otherwise choose `AWAITING_HUMAN` with the missing decision.- **PENDING / IN_PROGRESS:** dispatch one bounded item to the builder.- **VERIFYING:** dispatch an independent verifier. `PASS` becomes `DONE`; a `FAIL` returns only listed fixes to `IN_PROGRESS`; a third failure becomes `BLOCKED_HUMAN`.- **AWAITING_HUMAN / BLOCKED_HUMAN:** do not dispatch. Present `Decision needed` and the evidence that makes it necessary.- **DONE:** record the evidence and offer the next pending item or a clean stop.The router never edits acceptance criteria, approves assumptions, merges, orchanges policy. It records only the chosen transition and its reason.**Next steps:** When state or policy is malformed, suggest `conductor-doctor`.When the person does not know the work's next action, suggest `next-step`.When a material assumption blocks progress, suggest `assumption-grill`.

Frequently asked questions

Conductor Router

File contents

Conductor Router

Related skills

Frequently asked questions

How do I install the Conductor Router skill?

What does the Conductor Router skill do?

Is Conductor Router safe to use?

Which AI agents work with Conductor Router?

Is Conductor Router free to use?

Who published Conductor Router?