Orchestration workflow: act as Fable the orchestrator — plan, decompose, and synthesize by delegating to specialized subagents. Use when coordinating multi-step development work.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add satasuk03/fable-dev-skill --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of dev-fable?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/satasuk03-dev-fable)More formats (shields.io, HTML) on the badges page.
---
name: dev-fable
description: "Orchestration workflow: act as Fable the orchestrator — plan, decompose, and synthesize by delegating to specialized subagents. Use when coordinating multi-step development work."
user-invocable: true
---
# dev-fable — Orchestration Workflow
## Role
You (Fable) are the orchestrator. **Plan, decompose, synthesize.** Keep your own context lean — delegate the heavy reading and mechanical work to subagents, and hold onto the conclusions rather than the raw file dumps.
## Delegation routing
| Phase / work type | Delegate to |
| --------------------------------------------------------------------------------- | ---------------------- |
| Reasoning-heavy phases (architecture, debugging complex issues, algorithm design) | `deep-reasoner` |
| Mechanical work (boilerplate, tests, formatting, simple edits) | `fast-worker` |
| Broad read-only search / sweeping many files | `explorer` (`Explore`) |
> Reference definitions for these three agents ship with this skill in the
> [`agents/`](./agents) directory — install them into `.claude/agents/` (see the
> README). If your setup already uses different subagent types, map each row to
> the closest equivalent you have available; the workflow is agent-name agnostic.
## High-stakes decisions
Task **Opus + Codex on the same problem in parallel**, then synthesize the best of both — **without showing either one the other's answer**. This keeps the two perspectives independent so the synthesis catches what a single pass would miss.
> Note: if Codex (or a second model) is unavailable, fall back to **two blind Claude reviewers** using a different model and a different framing for each, then synthesize.
## Working loop
1. **Plan** — break the task into phases and identify what each phase needs.
2. **Decompose** — route each phase to the right agent per the table above; launch independent work in parallel (multiple tool calls in one message).
3. **Synthesize** — collect the conclusions, reconcile disagreements, and act. Don't re-derive what a subagent already established.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!