planning-with-files

You maintain project planning context across sessions by using persistent on-disk planning files. This approach automatically creates and updates task_plan.md, findings.md, and progress.md to capture goals, discoveries, and progress, ensuring stable memory remains available after interactions end.

A plan-first workflow for task management enforces starting from a defined plan before executing tools. It supports breaking down multi-step tasks into structured phases and uses hooks to refresh goals, enabling automatic session recovery after interruptions.

You track task progress using markdown files by writing to a structured on-disk workspace. The system logs phase statuses, decisions, and errors into progress.md and findings.md, allowing you to outline phases and resume exactly where you left off.

Yes, you need the orjson dependency installed to use persistent planning files. This fast JSON library supports the underlying scripts that automatically create, update, and recover your task_plan.md, findings.md, and progress.md workspace files.

Yes, you can reset and recover a multi-step task after an interruption. The system applies automatic session recovery by reading the persistent markdown files, refreshing your goals, and restoring the exact phase status before the disruption.