promote-plan

Move execution plans between proposed, active, and completed directories using git mv to preserve file history. This aligns the plan location with its real-world state while updating cross-references across documentation.

Plan drift occurs when a plan's real-world state diverges from its directory state. You should update plan metadata and Status lines whenever work starts, progresses, completes, or when drift-detector flags trigger.

Yes, you can abandon or revert active execution plans safely when work is halted or superseded. The process moves plan files and updates cross-references to maintain overall documentation consistency.

Yes, promoting a plan with git mv preserves file history and fixes cross-references across docs. It ensures a Status line is present and updated so that documentation accurately reflects reality.

The best way to fix execution plan drift is to move plan files to the correct stage directory using git mv and update their Status lines. This resolves location mismatches flagged by drift-detector triggers.