planning-with-files

Track multi-step tasks across breaks by maintaining persistent planning artifacts like task_plan.md, findings.md, and progress.md. These files log phases, discoveries, and session details to automatically recover context and guide decisions after interruptions.

Persistent planning for long-running sessions is the process of using markdown files to store task plans, findings, and progress logs. It automatically refreshes goals before tool usage, enabling continuous workflows despite interruptions or context limits.

Initialize planning files for a complex project by creating task_plan.md, findings.md, and progress.md in your project directory. Use provided templates and scripts to bootstrap the planning structure and enforce frontmatter-driven identity for repeatable workflows.

Yes, you can use markdown templates for automatic session recovery. The templates structure your task_plan.md, findings.md, and progress.md files, allowing the system to re-read plan files, refresh goals, and safely recover context after interruptions.

Context management works with multiple tool calls in research scenarios by automatically re-reading plan files to refresh goals before each tool usage. This ensures safe context management and maintains decision accuracy throughout long-running sessions.

Limitations of using markdown files for workflow planning include the need to enforce frontmatter-driven identity manually for consistency. While templates and hooks support repeatable workflows, complex project execution still requires strict adherence to the file structure to avoid context loss.