dispatcher
SolidUse when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one via AskUserQuestion, atomically claims it, and routes you to the chosen entry command. Triggers: "what should I work on next", "dispatch me to a repo", "pick the next project", "run /dispatcher". <example>Context: operator finished a session and wants the next-best repo across the portfolio. user: "/dispatcher" assistant: "Ranked 18 free repos — top recommendation: Pencil-Designs (score 4.50, 90d stale). Confirm via the picker, I'll claim its lease atomically, then route you to /session deep."</example>
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Kanevry
- Repository
- Kanevry/session-orchestrator
- Created
- 5 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
_dispatch
Core router. Always active. Auto-invokes matching skill before every response. Runs confusion protocol on high-risk ambiguity.
orchestrator
TRIGGER when: «оркестратор/orchestrator», «старшая/младшая модель», «делегируй/delegate», «Mode A/B», «file-prompt», «umbrella», «батч правок/batch fixes», «пакет фиксов»; ИЛИ первая из серии мелких правок одной темы; ИЛИ задача распадается на ≥3 независимых подзадач; ИЛИ «автономно / волнами / работай без остановок / прогони очередь кикофов сам» при ≥2 kickoff'ах → Queue mode. SKIP: тривиальная правка по точному пути (≤5 строк, 1 файл).
dispatch-helpers
Use whenever the orchestrator is about to issue a raw Agent() / Task() dispatch to a devt:* subagent (single OR parallel) instead of routing through /devt:review or /devt:workflow. Surfaces two CLIs that build the canonical envelope so context blocks (scope_trust, scope_hint, memory_signal, governing_rules) are never silently dropped — `dispatch run agent --task=...` for one-off single dispatches, `dispatch render-filled agent:auto` for advanced cases (lane fan-out, pre-computation, custom edits). Trigger phrases include single dispatches like "dispatch devt:code-reviewer to review X", "run devt:programmer for Y"; fan-out like "fan out review across files", "parallel reviewer across communities"; recovery like "re-dispatch programmer with continuation".