Keep multi-file work coherent and reviewable.
1. Inspection phase
Have the agent identify current flow and likely edit locations before changing code. Challenge assumptions when the proposed plan conflicts with the repository.
2. Incremental edits
Implement one coherent behavior at a time. Avoid combining feature work with unrelated renames, dependency upgrades and formatting sweeps.
3. Tool actions
Review the scope of requested terminal or external-tool operations. Available integrations do not imply that every action is required for the task.
Worked scenario
A simple empty-state change does not require upgrading the Compose version. The patch stays focused on rendering and its test.
Apply it
Execute a small task, then explain the purpose of every changed file.
Check your understanding
The implementation stays within the acceptance criteria and necessary supporting changes. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.