From fable-discipline
Use when maintaining project state across sessions — writing or reading a STATE.md / MEMORY.md, recording what was learned, resuming work, or deciding what to persist. Establishes the 5-stage memory progression (Fail → Investigate → Verify → Distill → Consult), the write-before-walking-away / read-at-session-start rules, and marking every fact with how it was verified.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fable-discipline:compounding-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A stateless model only compounds if the environment around it remembers. This
A stateless model only compounds if the environment around it remembers. This skill is the discipline that turns scattered notes into memory that actually gets consulted.
Good memory walks: Fail → Investigate → Verify → Distill → Consult. Weak memory stops at stage 1 (notes + guesses, never re-read). The win is reaching stages 3–5: facts that say how they were checked, rules consulted before re-deriving, and a resume pointer.
A state file with sections matching the stages:
## Verified facts # stage 3 — stop guessing; each line says how it was checked
## General rules # stage 4 — consult BEFORE re-deriving
## Open failures # stages 1–2 — work in progress, with a repro pointer
## Lessons learned # stage 4 — distillations
## Last session # stage 5 — resume pointer, not a restart
The single highest-leverage habit: every persisted fact carries how/when it was checked, not just the claim.
- The deploy job pushes schema via flyctl proxy. (Verified-by: read ci.yml:90-152, 2026-06-14)
- Rule count is 70. (Verified-by: grep samples.ts + test asserts toBe(70))
A claim without a Verified-by: is a guess until proven — treat it as stage 1,
not stage 3. Recalled memories reflect what was true when written; re-verify a
named file/flag/count before relying on it.
Persist: non-obvious facts, decisions + their rationale, corrections/feedback, durable gotchas, resume pointers. Don't persist what the repo already records (code structure, git history, things in CLAUDE.md) or what only mattered to one conversation. One fact per memory; link related facts.
See PROVENANCE.md for sources.
npx claudepluginhub petrkindlmann/fable-discipline --plugin fable-disciplineGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.