Name the outcome
Start with the result that should be different when the work is done. That gives every later decision something concrete to serve.
- What is stuck now?
- What would useful improvement look like?
- What is deliberately outside the request?
How it works
The useful question is not which tool to add. It is what should improve, what must stay visible, and where a person needs to decide.
The delivery path
Each step leaves a visible record for the next one: the result, the evidence, the cost, and the decision boundary.
Start with the result that should be different when the work is done. That gives every later decision something concrete to serve.
Trace the inputs, tools, evidence, and handoffs around that result. The smallest useful workflow is easier to review and improve.
The right tools, LLMs, and agents prepare the work in sequence. Each handoff keeps its evidence and status attached.
A person reviews the evidence, approves the next external action, and records what happened so the system gets better over time.
The human boundary
The system can prepare work without quietly acquiring authority to act outside the workspace.
Prepared
Research, drafts, evidence, and cost
Reviewed
The next decision and its tradeoffs
Approved
Messages, publishing, changes, and spending
The next useful move
Share the problem or workflow. The first conversation is about context, scope, and the next useful decision.