planning-with-files

Organize complex multi-step tasks using Markdown files by maintaining a task_plan.md for goals, notes.md for findings, and a final deliverable file. This file-based memory pattern separates objectives from evidence, preventing context drift during repeated tool calls.

File-based working memory uses persistent Markdown files to store task goals, progress, and findings externally. This approach minimizes context usage while keeping decisions aligned with the original intent across long-running research or development tasks.

Workflows lose coherence because context grows and attention drifts as tool calls accumulate. A read-before-decide loop that regularly re-reads a task_plan.md file restores attention and keeps multi-step progress aligned with original goals.

Track progress and errors by logging decisions and issues directly in a persistent task_plan.md file using checkbox edits. This error tracing and iteration approach supports recovery and continuous improvement throughout feature development.

You need a persistent Markdown plan for bug triage when a task requires repeated external tool interactions and checkpointing. It stores large content on disk to minimize context while preserving findings in notes.md for recovery.