当前：v6（2026-10-10）。 实时技能：fable-mode（根SKILL.md）， fable-opus，fable-sonnet，double-check，execution-guardrails。积分榜：俳句→ Opus → → 用户。fable-fable、fable-haiku 以及 v3 agents/ 路由 已退役——详见 SUPERSEDED.md。下面有相关章节介绍它们 被保留为历史。

克劳德在大型任务中的执行纪律：书面舞台地图，委派给 在运行时间允许的情况下，指定代理，每个阶段都进行验证检查，可以 实际上不及格，一个怀疑的自我评估，以及必须的冷核复核 任何东西都能送达。

它只是一个清单，不是能力移植。经过三次基准测试，所以要用README说明 可以说明它的作用和不的功能（见证据）。

梯子

每个等级一个技能，同一个核心循环，调校到该等级已知的失败模式：

fable-mode

Current: v6.1 (2026-10-24) — adds an error-first judgment check and a dissent check to step 3 for prose with no answer key (see bench/judgment/). Live skills: fable-mode (root SKILL.md), fable-opus, fable-sonnet, double-check, execution-guardrails. Ladder: Haiku → Sonnet → Opus → the user. fable-fable, fable-haiku and the v3 agents/ routing are retired — see SUPERSEDED.md. Sections below that describe them are kept as history.

Execution discipline for Claude on large tasks: a written stage map, delegation to named agents where the runtime allows, a verification check at every stage that can actually fail, a skeptical self-review, and a mandatory cold double-check before anything is delivered.

It is a checklist, not a capability transplant. Benchmarked three times so the README can say what it does and does not do (see Evidence).

The ladder

Haiku  →  Sonnet  →  Opus  →  Fable 5.1  →  the user

One skill per rung, same core loop, tuned to that tier’s known failure mode:

Two always-on companions:

• execution-guardrails — verify-before-flag, warning batching, word-boundary find-and-replace. Every model, every task, whether or not the loop runs.
• double-check — the delivery gate. A panel of fresh checker agents (Haiku for mechanical checks, Sonnet for requirements, Opus to adjudicate) attacks the finished artifact. Every fable runner calls it before handing anything over.

Core loop

1. Stage map first. Numbered stages, expected output each, one verifiable artifact per stage. Living document; at most two full replans per run — a third means the requirements are ambiguous, go back to the user.
2. Delegate by name. Reasoning stages to a Sonnet worker, mechanical stages to a Haiku worker, cold checks to a read-only verifier. Workers don’t spawn workers.
3. Verify with a check that can fail. A test that runs, a file in the expected shape, a source actually fetched, an output diffed against spec. “I reviewed it and it looks right” is not a check. Name the exact command or mark the stage unverified.