durable-session-state

Persist plans, decisions, evidence, and approval gates to durable files during long tasks.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill durable-session-state-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: durable-session-state
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/durable-session-state
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill durable-session-state-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long multi-phase AI sessions outlive their context window, and compaction summaries lose critical state: which diff a reviewer approved, what evidence was recorded, and which decisions are settled. This Skill persists that state to files so resumed sessions do not re-litigate settled decisions or treat stale approvals as current. ## Core Features & Use Cases - Four-file state model: Maintains plan.md, decisions.md, evidence.md, and gates.md per task, updated in place at phase boundaries. - Approval ledger with staleness checks: Records HEAD commit and diff summary per reviewer verdict so approvals can be invalidated when the code changes. - Resume protocol: Defines an authoritative re-read procedure after compaction, restarts, or handoffs, with artifacts taking precedence over conversation memory. - Use Case: During a long swarm-mode implementation with reviewer and critic gates, record each APPROVE verdict with its git HEAD; after a context compaction, compare the current HEAD against the ledger and re-run only the gates whose approvals went stale. ## Quick Start Ask the agent to persist the current task's plan, decisions, evidence, and gate verdicts to durable files before the context grows large.

Frequently Asked Questions about durable-session-state

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

FAQPage Schema
How do I preserve task state across context compaction in long AI sessions?

Write four small files per task: plan.md for scope, decisions.md for settled choices, evidence.md for validation results, and gates.md for approval verdicts. Update them at phase boundaries and before ending turns, treating the conversation as cache rather than storage.

How do I track reviewer approvals across code changes?

Record each verdict in gates.md with the git HEAD and a diff stat summary at approval time. On resume or before final synthesis, compare the current HEAD and diff against the ledger; if they differ, the approval is stale and the gate must be re-run.

Where should session state files be stored in a project?

Generic swarm tasks use .claude/session/tasks/<task-slug>/, while issue-tracer work uses .claude/issue-traces/<issue>/. Never write artifacts to the repo root or under .swarm/, and do not commit them unless the user asks.

What should I do first when resuming a compacted session?

Re-read the task's artifact files before doing new work; they are authoritative over conversation memory. Do not re-litigate settled decisions or redo proven work, and check gate staleness by comparing git HEAD against the latest APPROVE entry.

When should I not rely on durable session state files?

They are working state, not deliverables, so they add overhead for short single-phase tasks that fit within one context window. They also do not replace the issue-tracer skill's own schema, which takes precedence for its work.