From fable-mode
Checks multi-step work for promised-but-undone work, buried findings, and unverified claims before ending a turn. Enforces verification via four specific questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fable-mode:fable-turn-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before your final message, answer these four questions. A Stop hook
Before your final message, answer these four questions. A Stop hook enforces #1 mechanically — the goal is to pass BEFORE it fires.
critic agent with the claim and the diff; let
it try to refute before you assert.Then apply fable-voice to the final message itself.
npx claudepluginhub rennf93/opus-fable-playbook --plugin fable-modeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.