Preserve agent plans across context resets with Planning With Files
Gives coding agents a repeatable file-backed planning workflow using task_plan.md, findings.md, and progress.md so long-running work survives /clear, compaction, crashes, and handoffs.
npx skills add agentskillexchange/skills --skill preserve-agent-plans-across-context-resets-with-planning-with-files
## What the agent does
The agent installs and invokes Planning With Files when a coding task is large enough to need persistent state. It creates or reuses task_plan.md, findings.md, and progress.md, runs the documented lifecycle hooks, records findings as work proceeds, validates phase completion, and uses the repository’s instructions to re-inject the plan on each turn.
What this skill actually does
## When to use it
Use this when an agent is doing multi-step implementation, investigation, migration, or repair work where context loss would be expensive. It is especially useful before /clear, after compaction, when a session is resumed by another agent, or when a task needs an auditable completion gate.
## Operator actions
The repeatable agent workflow is to run planning setup, validate whether the work needs persistent files, review the active plan before each phase, automate context recovery through hooks, and manage completion without losing the task boundary.
## Scope boundary
This is not a general project-management app, a generic notes convention, or a broad planning framework. The workflow is specifically bounded to agent-operated planning files, recovery after context resets, lifecycle hook reminders, and deterministic progress tracking inside coding-agent sessions.
## Source evidence
The upstream repository documents the three-file pattern, lifecycle hooks, session catchup behavior, completion gates, command names, benchmark notes, and installation routes across Claude Code, Codex, Cursor, Gemini CLI, OpenCode, OpenClaw, and other Agent Skills-compatible runtimes.