continuity-ledger

Maintain persistent project state in a structured Markdown ledger file.

1|Updated Jun 18, 2025

Search Tags:#context management #agent coordination #project continuity #long-running tasks #state persistence #ledger

Ready to run

npx skills add https://github.com/knopki/dotfiles --skill continuity-ledger-knopki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: continuity-ledger
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/continuity-ledger
Command: npx skills add https://github.com/knopki/dotfiles --skill continuity-ledger-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that crucial project context, decisions, and state are preserved across agent interactions and context window limitations, preventing information loss in long-running tasks.

Core Features & Use Cases

Persistent State Management: Maintains a structured ledger (.opencode/CONTINUITY.md) that survives context window compactions.
Cross-Agent Coordination: Facilitates seamless handoffs and consistent state tracking between multiple agents.
Use Case: When working on a complex software project involving multiple agents, this Skill ensures that all agents have access to the latest project goals, constraints, and execution status, even after the conversation history is truncated.

Quick Start

Initialize the continuity ledger for the current project.

Frequently Asked Questions about continuity-ledger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain project state and context across context window compactions?▼

Maintain project state across context window compactions using a structured Markdown ledger file. This approach persists crucial execution status, decisions, and constraints externally, preventing information loss when conversation history is truncated during long-running tasks.

What is the best way to coordinate state tracking between multiple agents?▼

Coordinate state tracking between multiple agents by reading from and writing to a shared structured ledger file. This facilitates seamless handoffs, ensuring all agents access the latest project goals and execution status consistently without relying on direct conversation history.

How does a persistent ledger help with long-running workflow continuity?▼

A persistent ledger ensures long-running workflow continuity by storing project context externally in a Markdown file. It survives context window limitations and compactions, allowing agents to reload crucial state, decisions, and constraints after session interruptions or history truncations.

Do I need a specific file format for project state persistence across agents?▼

Yes, project state persistence requires adherence to a defined Markdown schema for ledger updates. The structured ledger file stores execution status and goals, ensuring consistent data tracking and seamless context retrieval across multiple agent interactions.

Can I use a structured ledger for cross-agent handoffs in complex software projects?▼

Yes, a structured ledger enables cross-agent handoffs in complex software projects by maintaining a shared persistent state. Agents access the latest constraints and execution status from the file, ensuring consistent coordination even after conversation histories are truncated.

When should I not use a single ledger file for agent context management?▼

Avoid using a single ledger file for agent context management if your workflow requires real-time concurrent writes without schema conflicts, as it relies on a structured Markdown format for sequential state tracking rather than handling high-frequency parallel updates.