Iterate Plan

Revise one existing implementation plan in place. The output remains a plan: inspect the repository and edit the artifact, but leave implementation work to the implementation phase.

Steps

1. Establish the revision set

Resolve exactly one target plan and all of its context:

1. Use the plan path supplied by the user or already established in the conversation. If it is absent, inspect the active .agent-work/tasks/<task>/ directory. Use a symlink-aware listing such as ls -La; task directories may be symlinks.
2. Read the entire plan, every user-supplied file, and every artifact in that task directory. Include ticket.md or task.md, research, design discussion, PRD or TDD, and structure outline files when present.
3. Inventory each requested change from the user's message and any supplied feedback file. Record its source, the affected plan section, and whether it states desired behavior, alleges a repository fact, or asks for a decision.
4. If the input contains an inline <comments> block, names artifact comments, relies on a ticket/comment file, or identifies only the plan without giving feedback, read feedback and decisions before classifying or acting on those items.

If no target can be distinguished among multiple plan files, ask the user to identify it and stop. If there is a target but no revision instruction or feedback, ask what they want changed and stop.

This step is complete only when one plan is selected, every available task artifact has been read, and every feedback item has a source, affected section, classification, and requested outcome or explicit unknown.