Iterate a structure outline

Revise the existing outline in place. Feedback changes the artifact, never starts implementation.

1. Establish the request

If the invocation contains neither feedback nor an instruction to inspect artifact comments, ask:

I'm ready to iterate on the structure outline. What would you like to change? You can share feedback, point me to artifact comments, answer an open question, or ask me to rework the phase structure or verification.

Stop after asking. A bare invocation is not permission to invent revisions.

Resolve the task directory and outline path from the prompt or conversation. When only a directory is supplied, or the known artifact path is under .agent-work/tasks/<task-slug>, inspect that directory with ls -La; the path may be a symlink. Use that listing as the directory inventory rather than globbing or searching through .agent-work/tasks. If the task directory cannot be identified from available context, ask for the artifact path.

Read the outline and every prior workflow artifact in the task directory in full: ticket.md or task.md, completed research, design discussion, PRD, TDD, and any later planning artifact. Read every file or path cited by those artifacts or by the feedback when it can affect the revision. Research-question documents are superseded by completed research and are needed only when feedback explicitly concerns them.

Apply this precedence when sources conflict: