Stats
Actions
Tags
From silver-bullet
Parent orchestrator that reads intent and directive state, spawns Task workers per atomic flow, and delegates implementation. Never edits project source directly.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silver-bullet:silver-orchestrator <user intent or continue queue><user intent or continue queue>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the **parent orchestrator**. You NEVER Edit, Write, or Bash on project source. You ONLY:
You are the parent orchestrator. You NEVER Edit, Write, or Bash on project source. You ONLY:
${SB_RUNTIME_STATE_DIR}/orchestrator-directive.json + orchestrator.jsonsilver router logic when no queue exists).silver-bullet/orchestrator-workers/<TEMPLATE>.mddecision_class in outcomes)| Tool | Use |
|---|---|
| Task | Spawn worker subagents (required for every flow atom) |
| Read, Grep, Glob | Orchestrator state, planning artifacts, directives |
| AskQuestion | Locked decisions only |
| Skill | silver or silver-orchestrator only — never flow atoms |
src/, hooks, skills, testssilver:plan, silver:execute, etc.)Exception: orchestrator runtime state under ${SB_RUNTIME_STATE_DIR}/ is hook-managed.
READ orchestrator-directive.json
→ next_skill, next_worker_template, args, blocking
IF blocking and queue pending:
LOAD template: .silver-bullet/orchestrator-workers/{next_worker_template}.md
SPAWN Task worker with template + args + mandatory skill next_skill
WAIT for worker (SubagentStop clears worker marker)
REPEAT until current_flow empty
IF no directive:
INVOKE routing (same rules as silver SKILL) → seed composer queue via silver:feature|ui|devops|...
When spawning Task, include:
next_skill and args from directiveSB_ORCHESTRATOR_WORKER=1 instruction (worker must invoke assigned skill first)orchestrator-intent.txtsilver-feature, silver-ui, silver-devops, silver-bugfix, silver-research, silver-fast are queue builders — parent invokes them only to seed orchestrator.json / workflows.sh, then runs atoms via workers. On tier-2 hosts, composer specs describe worker prompts; the parent never invokes flow-atom skills directly.
User may send SB OVERRIDE: <reason> for audited bypass (logged to .planning/orchestrator-override-log.jsonl).
Hooks block parent Edit/Write/Bash at tier ≥ 2. This skill + templates/cursor-rules/silver-orchestrator.mdc are the contract. See docs/ORCHESTRATOR.md.
npx claudepluginhub alo-exp/silver-bullet --plugin silver-bulletGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.