continuous-planner

A persistent three-file plan uses task_plan.md, findings.md, and progress.md to store decisions and progress, ensuring continuity when switching models. This pattern survives interruptions and maintains a single source of truth for long-running projects.

The three-file pattern for project management splits information into task_plan.md for planning, findings.md for discoveries, and progress.md for tracking. This structure provides a durable decision log and single source of truth for coordinating work across different AI models.

To start a continuous plan, trigger the command "cp" to automatically generate the three required files: task_plan.md, findings.md, and progress.md. This initializes a persistent planning structure for your project and integrates Beads-driven progress tracking.

Yes, Beads integrates with persistent markdown project plans to drive progress tracking and checkpointing. It reflects decisions and updates over time directly within the progress.md file of the three-file structure.

A three-file continuous plan is specifically designed for long-running projects requiring cross-model coordination. The durable files serve as a shared decision log, maintaining continuity and single-source-of-truth accuracy despite frequent model switches.

A continuous three-file plan should not be used for short-lived, single-session tasks that do not require durable decision logs or cross-model coordination. It is built for long-running projects where maintaining persistent continuity across interruptions is essential.