memory-continuity

Memory Continuity Skill

Use this skill to preserve high-value context between clean sessions while avoiding noisy or low-signal carryover.

Storage Layout (Hybrid Contract)

Use this deterministic structure:

.agentic/
  memories/
    MEMORY.md
    index.md
    snapshots/
      YYYY-MM-DDTHH-MM-SSZ.md

Rules:

• If .agentic/memories/ does not exist, create it and required child paths.
• MEMORY.md is the current canonical continuity file.
• index.md is a small pointer log to snapshots.
• snapshots/ stores timestamped continuity checkpoints.
• Use memory-current-template.md for MEMORY.md initialization.
• Use index-template.md for index.md initialization.

First-Run Initialization and Bootstrap Rules

When MEMORY.md and index.md do not exist:

1. If there is active iteration context (for example an open issue/PR, active branch work, or already-decided next steps), initialize both files from templates immediately.
2. If there is no active iteration context, inspect commit history for signal:

• if history is rich enough to derive meaningful continuity, ask the user before generating a brief bootstrap memory from commits;
• if history is not rich enough, ask the user before leaving memory uninitialized.

1. Never invent synthetic history. If signal is insufficient, state that explicitly.

Start-of-Session Retrieval Workflow

1. If files are missing, apply First-Run Initialization and Bootstrap Rules.
2. Read .agentic/memories/MEMORY.md if present.
3. If index.md exists, read only the latest 1 to 3 snapshot pointers.
4. Extract only high-signal items:

• current objective
• decisions made and rationale
• open risks/questions
• next concrete steps

1. Do not import verbose logs, full transcripts, or resolved low-impact details.

End-of-Session Update Workflow

1. Create directories/files if missing:

• .agentic/memories/
• .agentic/memories/snapshots/
• .agentic/memories/MEMORY.md (from memory-current-template.md)
• .agentic/memories/index.md (from index-template.md)

1. Build a new memory entry using memory-template.md.
2. Update MEMORY.md additively:

• keep existing unresolved items
• append new high-signal updates
• remove or compress resolved/noisy items

1. Write a timestamped snapshot:

• filename format: YYYY-MM-DDTHH-MM-SSZ.md

1. Append one row in index.md pointing to the snapshot and objective.