planning-with-files

Track complex tasks by maintaining persistent markdown planning files like task_plan.md, findings.md, and progress.md to store goals, phases, and research for context recovery and auditing across long-running sessions.

Manage context recovery using a structured workflow that automatically catches up sessions and restores context by reading progress.md and findings.md before making decisions.

Create a task_plan.md file in your project root to establish the planning backbone, then update phase statuses like pending, in_progress, and complete as you progress through the debugging session.

Yes, markdown planning files enforce phase governance by using status markers and a read-before-decide pattern to maintain focus, trace decisions, and coordinate multi-step tasks effectively.

You need persistent markdown files for task management when working on long research tasks, complex projects, or debugging sessions that require tracking phases, findings, and progress across many tool invocations.

Yes, this multi-step task planning approach works without external dependencies, relying solely on scripts to coordinate phases and update markdown files for tracking progress and findings.