planning-with-files

Multi-step research tasks are managed by enforcing a persistent three-file pattern: task_plan.md for goals, notes.md for findings, and a final deliverable file. This file-backed workflow anchors project phases and maintains progress updates after each execution step.

Structuring extended project workflows requires a loop-based approach using Markdown files. You create task_plan.md to define phases, save intermediate outputs to notes.md instead of context, and update the plan iteratively to guide planning, research, execution, and delivery.

A file-backed planning workflow is needed for non-trivial, multi-step projects or long-running tasks. It is applicable when work spans multiple tool calls and requires storing large outputs in persistent Markdown files rather than temporary context to prevent data loss.

Organize task planning by creating task_plan.md with a defined goal and phases, record research findings in notes.md, and compile the final output into a deliverable file. Update the task_plan.md after each phase to maintain a structured project workflow.

Yes, persistent Markdown files organize complex project deliverables by separating goals, notes, and final outputs into a three-file pattern. This approach transforms complicated tasks into a repeatable workflow, ensuring deliverables and research are systematically tracked.

The three-file pattern requires manual updates to task_plan.md after each project phase and strict adherence to saving large outputs to files. It is less suited for simple, single-step tasks that do not require organized notes or extended research tracking.