02 / Shape the work
One task. One visible improvement.
Small tasks keep a coding assistant grounded and make human review more useful. Split work by behavior rather than arbitrary file counts. A single coherent change may touch a component, a validator, and a test without becoming three unrelated assignments.
Find the smallest complete slice
For a saved filter feature, begin with restoring one existing filter from the URL. Add editing and persistence in later tasks if those behaviors can stand alone. Each slice should have an observable result; "write half the service" is a progress marker, but it is difficult to verify on its own.
Keep a stop condition in the packet
Include the behavior, relevant context, allowed scope, and evidence you expect. Ask the assistant to stop and explain when an assumption fails, such as a missing endpoint or an incompatible data shape. When a task grows unexpectedly, revise the packet before stacking more implementation on an uncertain foundation.
A starting prompt
Task: Restore the status filter from the URL. Use the existing query parser and filter component. Preserve unknown query parameters. Check: refresh, empty status, and an invalid status. Stop if the current routing API cannot support this.