planning-with-files

Persistent file-based planning maintains context for complex tasks by writing goals, findings, and session logs to task_plan.md, findings.md, and progress.md. It automatically restores state after interruptions or a session clear by re-reading these on-disk files.

File-based planning organizes work by capturing goals, research, and session progress in persistent markdown files. You need it for complex projects or research tasks requiring more than five tool calls, ensuring goals stay aligned across long workflows.

Set up persistent planning files by generating task_plan.md, findings.md, and progress.md from provided templates. Bootstrap the workflow using included scripts, then re-read the task_plan.md file before making any tool decisions to maintain alignment.

Yes, file-based planning supports automatic session recovery for interrupted research. It logs session progress in progress.md and findings in findings.md, allowing the workflow to restore its previous state and resume the multi-step project seamlessly.

Using markdown templates enforces a planning-first workflow that prevents context loss in long tasks. Unlike relying on volatile context, persistent on-disk files track phases, research, and logs, allowing you to audit progress and recover state after interruptions.

Yes, file-based planning is specifically designed for complex projects spanning many tool calls. It tracks phases in task_plan.md, re-reads the plan before each tool use, and provides scripts to bootstrap, recover, and audit the planning data.