Controlled implementation is a sequence of checkpoints
Implementation should follow the accepted task boundary and plan. Keep discovery, editing, verification, and handoff visible so a reviewer can tell what actually happened.
A small diff is a control surface: it limits unrelated risk and makes recovery easier.
| Checkpoint | Question |
|---|---|
| Before edit | Is the scope and starting state clear? |
| During edit | Is each change tied to the plan? |
| After edit | Does the diff match the intended behavior? |
| Before handoff | Are checks and unknowns recorded? |
Implementation loop
- Confirm status and task boundary.
- Make one small change.
- Inspect the diff immediately.
- Run the narrowest useful check.
- Update the plan or evidence with facts.
- Stop and ask when scope or behavior changes.
Implementation record
Step: <name>
Files: <list>
Change: <purpose>
Check: <command and result>
Unknown: <remaining limit>
Next: <smallest action>Canonical lesson source · JavaRush
Open JavaRush material