Practical Application

Use the following workflow before assigning implementation to an agent:

1. State the mission. Describe the real outcome the work is intended to produce, not merely the file

that should change.

1. Identify consequential decisions. Separate decisions that require product, security, or

architectural judgment from decisions that are routine implementation details.

1. Resolve the hard decisions. Decide the intended boundaries, interfaces, and validation approach

before asking the agent to write code.

1. Create a task packet. Include the objective, relevant context, in-scope and out-of-scope areas,

expected interfaces, tests, and completion criteria.

1. Choose the interaction mode. Keep planning, ambiguous work, and complicated decisions

human-in-the-loop. Delegate well-scoped implementation to an away-from-keyboard agent when appropriate.

1. Review against the mission. Do not limit review to whether the code runs. Check whether the

result solves the intended problem and fits the roadmap.

For example, a request such as "build the application" transfers too much strategy to the agent. A stronger sequence is to define the user problem, choose the first useful capability, decide the system boundaries, specify a small implementation task, and then delegate that task.