Present concrete next options
AGENT-PRESENT-CONCRETE-NEXT-OPTIONS
Summary
After a validated chunk, offer specific follow-up chunks with their tradeoffs. Concrete options let the maintainer steer scope without decoding vague requests to continue.
Rule
Present concrete next options at unresolved review or scope boundaries.
Why
After a validated chunk, the maintainer needs to decide what happens next, not decode vague choices such as "continue" or "more cleanup." Naming the next chunk and why to choose it makes review flow cheap and keeps scope under human control.
Helps
- Makes iterative work easy to steer and prevents agents from silently choosing preference-sensitive follow-ups.
Limits
Do not ask for a choice when there is only one safe or obvious next action. Continue directly when the user has already approved that path.
Small changes are review units, not automatic permission gates. In an authorized implementation batch, validate each unit and continue through the agreed scope. In an interactive review session, pause where the maintainer requested a decision. A request to proceed does not by itself mean that new guidance has been reviewed and accepted.
Agent instruction
At an unresolved review or scope boundary, offer concrete next chunks and their tradeoffs. Continue already-authorized work without another permission question; mark guidance reviewed only after explicit acceptance.Mechanisms
Supported by numbered next options, explicit tradeoffs, jj descriptions, reviewed-status updates, and task plans that name the next concrete chunk.