Agree on the problem before solving it.
Start with the user outcome and the existing system. Read the relevant source, decisions, and constraints. Name the behavior that must change and the behavior that must remain stable.
A practical engineering loop that carries intent from the initial brief through implementation, verification, and handoff.
Click through a retry-safe checkout mission. This is an illustrative scenario with example data.
“Add retry-safe payments. Keep the existing API contract. Show me the tests before we ship.”
Start with the user outcome and the existing system. Read the relevant source, decisions, and constraints. Name the behavior that must change and the behavior that must remain stable.
Split the work into bounded tasks and identify dependencies. Independent work can progress together; dependent work waits for its prerequisites. Record who owns each task and what will close it.
Specialists implement their assigned scope. Capture important decisions as the work evolves, preserve unrelated changes, and make deviations visible instead of silently widening the task.
Choose checks appropriate to the change. A static preview, a compiled binary, a database check, and an end-to-end run answer different questions. Record actual results and unresolved gates.
Bring the changed files, test results, open questions, and continuation state together. Keep release approval explicit. The next engineer or session should be able to pick up without reconstructing the work.
A blocker is useful information. A failed test is useful information. Record it, revise the bounded task, and make the next step clear.
Keep the failure with the task, understand what it proves, and address the specific cause. Re-run the relevant checks after the change. Do not turn a partial result into a broad acceptance claim.
Work whose inputs and file ownership are sufficiently independent. The dependency plan should decide the order; increasing the agent count alone does not make a task independent.
In scope, tradeoffs, acceptance criteria, consequential operations, and release decisions. Each handoff should identify the exact decision that is needed.
Tell us what you want to change, what must stay stable, and what success looks like.