continuity-ledger
Skill0 starsChanged 4 months agoMITView on GitHub
Keep substantial work coherent across long sessions or compaction with one short factual `CONTINUITY.md` covering sources of truth, goal, constraints, decisions, evidence, and done/now/next state. Use when session drift would otherwise become a real risk.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Tivaphe/hermes-worldbible-skillstheir own version, first seen Oct 20, 2026
- parcadei/Continuous-Claudetheir own version, first seen Oct 17, 2026
- parcadei/Continuous-Claude-v2their own version, first seen Oct 8, 2026
- parcadei/Continuous-Claude-v3their own version, first seen Jan 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- Tivaphe/hermes-worldbible-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not use when: an existing issue, brief, or spec bundle already serves as current durable state and no extra memory layer is needed.
- Distinctive: line 14
Keep one compact, factual continuity file that lets the next session resume work without reconstructing the project state from chat history.
- Very specific: line 18
Read the current CONTINUITY.md before substantial work and update it only when goals, constraints, decisions, evidence, or done/now/next …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Continuity Ledger
Metadata
- Trigger when: the task is long enough, branchy enough, or interruption-prone enough that chat memory is no longer a safe source of truth.
- Do not use when: an existing issue, brief, or spec bundle already serves as current durable state and no extra memory layer is needed.
Skill Purpose
Keep one compact, factual continuity file that lets the next session resume work without reconstructing the project state from chat history.
Instructions
- Gate the need for a ledger first. If a better durable artifact already exists and is current, reuse it instead of creating a second memory layer. When you do need a ledger, read
~/.codex/skills/continuity-ledger/references/template.mdfor the minimal section set. - Read the current
CONTINUITY.mdbefore substantial work and update it only when goals, constraints, decisions, evidence, or done/now/next state actually changed. Keep it short, factual, and bullet-based. - Validate the ledger. Mark uncertain items as
UNCONFIRMED, update higher-authority source artifacts first when architecture or test state changed, and make sure the ledger points back to those sources instead of duplicating them.
Non-Negotiable Acceptance Criteria
- At most one repo-local continuity ledger exists for the task.
- The ledger contains stable facts and actionable status, not chat transcript or vibes.
Done,Now, andNextare explicit and current.- The ledger is a bridge to the real source artifacts, not a shadow PRD.
Output
- An updated
CONTINUITY.mdpath. - A short summary of changed sections, especially decisions and
Done/Now/Next. - Any unresolved question that still blocks confident continuation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.