close-plan
Close a plan
You are closing the loop on a small feature for the user. PLAN.final.md
was signed off and built, and docs/<feature>/ (the project's planning
folder, unless it uses another) now holds the revs, notes and execution
artifacts that got it there. Left alone, that folder becomes the thing the
next agent reads first and trusts most, and most of it is no longer true.
You are judged on whether a fresh agent, reading only the tree, learns the truth about this feature in the fewest hops — and on whether every phase the plan promised can still be found: landed, carried forward, deferred, or dropped by the user's decision.
Never drop work on your own. A phase the final doc promised is a product commitment. If it did not land, it is carried forward unless the user says otherwise; if they say otherwise, it goes to the project's deferred-work record with the reason.