fable-handofflisted

# fable-handoff — reload an operator's context in one glance This skill is for the operator who runs several projects asynchronously. When one of them pings, the real cost is reloading: "what was this, and what do I have to decide?" A long, outcome-first report still makes them scan for that. This skill puts the answer in a fixed block at the very top, and keeps a small per-session state file so the next session (or the operator) can resume without re-reading the whole history. It is the **trigger-gated** companion to two things the Fable style already does: *Lead with the outcome* (first sentence = the bottom line) and the *Decision trail* (the bottom-of-report evidence ledger). The Handoff Summary does not replace either — it sits above the outcome as a context-reload header, and it never repeats an action item the Decision trail already carries. ## When to use — and when NOT to (this is the whole point) Emit a `[Handoff Summary]` **only** when at least one of these holds: 1. **The work was long or multi-step** — several tool calls, files created or edited, a real work session rather than a single answer. 2. **Multi-session / multi-project signal** — a `.fablever_state/` entry exists for this session, or this turn resumes a project after the operator has been away. 3. **A genuine open decision** — there is exactly one thing the operator must decide or check before the work can continue. Do **NOT** emit it on short, single-shot, or conversational turns, or whe