The gap
The plan created with the Plan tool (“Cursor plan”) has a build/execution function (todos, run, etc.) but lives in Cursor’s plan storage and isn’t editable or updateable during the chat. The detailed, iterative plan we actually refined lives in the workspace (e.g. docs/PLAN_SPREADSHEET_IMPORT.md), which doesn’t have the build/tracking UI. So:
-
The plan that drives execution isn’t the one that gets updated from questions and feedback.
-
Users have to choose: use the Cursor plan (good for execution, bad for iteration) or a workspace doc (good for iteration, no build/tracking).
What would fix it
The Cursor plan should be editable and updateable in line with the conversation:
-
Edits to the plan (from user questions, feedback, or AI refinements) should update the same plan that has the build function, not a separate doc.
-
Ideally: one plan artifact that is both the source of truth for execution/todos and the living document that gets revised as we clarify scope, hierarchy, storage, etc.
Impact
Right now it’s confusing that “the plan” with build/todos and “the plan” we keep updating are different things. Making the Cursor plan editable and keeping it in sync with the conversation would close that gap.