# Fable Loop

End-to-end orchestrated workflow that runs a task the way Fable ran sessions - parallel...

- Repository: https://github.com/Sahir619/fable-method (2311 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-03
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Sahir619/fable-method --skill fable-loop -g -a claude-code -y`
Codex: `npx skills add Sahir619/fable-method --skill fable-loop -g -a codex -y`
Cursor: `npx skills add Sahir619/fable-method --skill fable-loop -g -a cursor -y`
Gemini CLI: `npx skills add Sahir619/fable-method --skill fable-loop -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Sahir619/fable-method`

## Description

End-to-end orchestrated workflow that runs a task the way Fable ran sessions - parallel evidence subagents, one committed plan, surgical execution with an intent gate, adversarial verification agents, honest outcome-first report. Use for non-trivial multi-step tasks when the user says "/fable-loop", "run the fable loop", or "do this the way Fable would". For the rules alone without orchestration, use fable-method; for large multi-phase projects, prefer the GSD workflow and use this inside phases.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# The Fable Loop

This skill orchestrates the fable-method: read its SKILL.md first; its rules govern every stage. It is installed alongside this skill (in this plugin's `skills/fable-method/` directory, or `~/.claude/skills/fable-method/` for manual installs). The method says WHAT to check; this loop says WHO does the work: what runs in the main thread, what fans out to subagents, and what gets attacked before delivery.

**Gate first.** Trivial per the method's triviality gate: just do it, verify with the one obvious check, report in two sentences. No stages, no subagents. Everything else runs the four stages below in order.

## Stage 1 - PLAN (the first bookend)

1. Apply method Steps 0-3: classify the ask, define done with a named verification, state load-bearing assumptions.
2. **Evidence fan-out.** Spawn the evidence gatherers as parallel subagents in ONE message, never sequentially:
   - codebase questions: an Explore agent per distinct area ("how does X work", "what depends on Y");
   - library or fact questions: a research agent that fetches current docs or searches the web;
   - each subagent returns distilled findings with citations, never raw file dumps.
   One batch plus one follow-up batch is the budget; a third needs a stated reason.
3. **Produce the plan artifact** in this shape: classification; definition of done plus its verification; evidence found (cited); ONE recommended approach (alternatives dismissed in a line each); the scope (the exact files or surfaces the work will touch); risks and assumptions; and the execution checklist.
4. **Decision gate.** Task-shaped and reversible: proceed to Stage 2 without asking. Plan-first shape (ambiguous scope, irreversible or outward-facing actions, or the user asked for a plan): present the plan artifact and STOP for approval.

## Stage 2 - EXECUTE

The rest: https://github.com/Sahir619/fable-method/blob/HEAD/skills/fable-loop/SKILL.md