Amending a Plan

Plans drift. New information appears mid-loop; reviewers raise concerns; the implementation reveals assumptions that were wrong. /code:amend-plan changes a plan.json plan without starting it over. Run it in Claude Code in your terminal, not in the Desktop app or the web app.

When to amend

• A teammate leaves a review comment that changes the scope.
• An open question got answered in a design review.
• The first implementation pass revealed a missing task.
• You want to cut scope and ship sooner.

The command

/code:amend-plan --workdir [path] --message "<text>" [--state-file [path]]

The amend handler recognizes four intent types:

• Directive – "add a task to migrate the old sessions table"
• Question – "what happens if the migration fails halfway?"
• Confirmation – "yes, remove task 3"
• Unstructured input – meeting notes or pasted threads, delegated to amend-extractor to pull out the changes

Amendment state is persisted in amend-session.json (in the workdir unless you pass --state-file) so a multi-turn amendment can continue across runs. Applied amendments are recorded in the plan's amendments array.

Best practices

• One message, one intent. Long amendments get classified less reliably.
• Reference tasks by their ID from the plan rather than paraphrasing.
• Use /code:amend-plan iteratively during the plan review checkpoint instead of regenerating the plan from scratch.

Related reading