planning-with-files

Write the plan to a persistent file like task_plan.md and re-read it before major decisions. This keeps goals in the model's recent attention window even after dozens of tool calls, preventing the lost-in-the-middle effect.

The Skill stores task_plan.md, findings.md, and progress.md in your project directory. On a new session, a catchup script scans the previous session transcript for unsynced context, then you run git diff and update the planning files before continuing.

Use it for tasks with three or more steps, research work, or anything spanning many tool calls. Skip it for simple questions, single-file edits, or quick lookups where persistent state adds no value.

Yes. It ships PowerShell scripts (init-session.ps1, check-complete.ps1) alongside bash versions, and the session-catchup.py script parses both Claude Code and Codex session transcripts to find unsynced context.

A PreToolUse hook re-reads task_plan.md before every tool call, so untrusted web content written there would be repeatedly injected into context, amplifying prompt injection risk. External content belongs in findings.md only.