Skip to content

Workflow: Update Long-Term Plan

Trigger: At the end of every significant "Phase" or "Sprint" (e.g., every 5-10 tasks), or when the user changes strategic direction.

Goal: Ensure architecture/LONG_TERM_PLAN.md reflects the reality of the project, not just a stale roadmap.

Steps

  1. Read the Current Plan

    • Read architecture/LONG_TERM_PLAN.md.
    • Read task.md (current progress).

  2. Analyze Progress

    • Mark completed phases as [Completed].
    • Update "Current Phase" pointer.
    • Add any new discoveries or requirements that emerged during execution.

  3. Update the File

    • Use replace_file_content or write_to_file to update architecture/LONG_TERM_PLAN.md.
    • Crucial: Do not just append. Refactor future phases if they are no longer relevant.

  4. Verify Consistency

    • Check if architecture/README.md or architecture/START_HERE.md needs a nudge to point to the new status.

// turbo 5. Commit the Update _ git add architecture/LONG_TERM_PLAN.md _ git commit -m "docs: update long-term plan status"