$npx -y skills add mrtooher/fable-mode --skill fable-haikuRun fable-mode execution discipline on Claude Haiku. Routes the task to the @fable-worker-haiku agent, whose definition carries the staged loop with tightened verification (no bare "unverified" allowed) and an escalate-don't-improvise rule. Trigger when the user explicitly asks f
| 1 | # Fable Mode — Haiku (v3, agent-routed) |
| 2 | |
| 3 | v3 change: the worker is a real agent definition (`agents/fable-worker-haiku.md`) |
| 4 | invoked by name. Its system prompt carries the loop, the tightened verification |
| 5 | rule, and the operational rules; this skill only routes. |
| 6 | |
| 7 | If a task has one obvious correct approach and fits in a single pass, skip this |
| 8 | loop and do it directly. |
| 9 | |
| 10 | ## How to run it |
| 11 | |
| 12 | 1. Confirm `fable-worker-haiku` appears in the available agent types. If not, |
| 13 | fall back to inline: spawn a general-purpose Haiku agent and pass it the |
| 14 | rules verbatim from `agents/fable-worker-haiku.md`. |
| 15 | 2. Spawn **@fable-worker-haiku** via the Task tool (`subagent_type: |
| 16 | "fable-worker-haiku"`). Brief it with: the task, the exact output path(s), |
| 17 | and the pass condition — name the check explicitly; Haiku gets no benefit of |
| 18 | the doubt on verification. |
| 19 | 3. Haiku is cheap: for independent sub-parts, fan out one worker per part and |
| 20 | merge. Set a ceiling on concurrent workers. |
| 21 | 4. Follow with **@fable-verifier** (a second Haiku is cheap; fresh eyes can't |
| 22 | inherit the worker's blind spots) for anything that will be delivered |
| 23 | without human review. |
| 24 | 5. If a worker escalates ("needs synthesis"), re-route that part to |
| 25 | fable-worker-sonnet rather than retrying Haiku with a louder prompt. |