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 after validated chunks.
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.
Agent Instruction
After a validated chunk, name the next concrete chunk and why to choose it so the maintainer
controls scope cheaply.Mechanisms
Supported by numbered next options, explicit tradeoffs, jj descriptions, reviewed-status updates, and task plans that name the next concrete chunk.