Agree on the outcome first
Before any work starts, settle what will be true when it is done. Ask questions only where something is unclear.
At Blume, the person and the agent agree on the outcome, in one sentence, before the agent plans or writes anything. It takes a minute.
What goes wrong without it
Straight to work
You type: “Add CSV export to the orders page.” Forty minutes later the agent shows a button that downloads every order in the system, with every column.
You wanted the rows shown by the current filters, with the columns on screen. Both readings were reasonable, and the agent’s tests pass for its version.
Outcome first
Before planning, the agent restates the request:
Outcome: a person on the orders page downloads the orders they are looking at as a CSV file.
One thing is unclear: should the export follow the current filters, or include all orders? I recommend following the filters.
You answer “filters, and only the visible columns”, and what it builds is what you meant.
A clear request (“Fix the typo in the pricing page title”) gets restated and goes straight on.
What to do
- Write it as a sentence about the product. “A person refunds an order from its page, fully or in part”, not “Refund work” or “Implement RefundService”.
- Say what is out. Scope left unsaid gets decided by whoever is typing.
- Ask only what is unclear. One or two real questions, each with a recommended answer.
- When the outcome changes, change it in the plan. A different outcome is a new delivery.
In Blume
- Every delivery begins in the Start phase, which ends when the outcome is agreed.
- The agent’s questions reach you as requests, each with options and a recommended answer.
- The outcome is the first section of the plan, before the acceptance checks and the tasks. With plan review, you see it again before the agent builds.