Revise an implementation plan while the agent works
Approve a bounded implementation, then add a requirement or correct a step while the agent works. Keep the feedback attached to the plan instead of burying it in another chat.
- Review the plan
- Send targeted feedback
- Inspect the revision
Before you start
- A task large enough to benefit from a plan, with acceptance criteria.
- An active or saved plan. These steps use the desktop plan workspace; terminal users can open it with /plan open.
- A decision about whether you want a light checklist or a full plan with code and before/after diffs.
Work through it
Approve the intended change
Ask for a plan before implementation. Inspect the files, steps and verification checks. Request a revision if the scope is wrong; use Implement only when you are ready for execution.
Check: For a full plan, review the included code snippets and before/after changes as well as the checklist.
Attach feedback to the right step
Open the plan workspace and add a point or comment. While a turn is running, the engine sends that feedback through steering. During review, feedback requests a revision rather than granting approval.
Check: Check the delivery receipt. A draft is not sent until you submit it.
Verify what changed
Read the revised plan and follow its progress. If no turn is running, the feedback remains with the plan for continuation. Inspect the eventual diff against the updated acceptance criteria.
Check: A delivered comment is not proof that the requested code change is complete; check the result.
Feedback follows the plan’s state
Before approval
Request a revised plan rather than starting the wrong implementation.
During execution
Send feedback through steering for the agent to read as it continues.
While idle
Keep feedback with the plan and deliver it when work resumes.
A prompt to adapt
Replace the task details with your own. This is a suggested instruction, not a recorded result or a security policy.
Plan this change before editing. Include the files in scope, steps and acceptance checks. Preserve the public API. Wait for approval; if I add feedback during execution, revise the remaining plan before expanding the scope.Keep these boundaries clear
Open the detailed guides
Checked against the documentation on .