01 / Goal
A task is not one prompt
A good development task names the goal, boundaries, relevant files, acceptance checks, and places the agent should not touch.
02 / Context
Context should be replayable
When an agent reads code, runs tests, and inspects the browser, it should leave an understandable evidence trail.
03 / Verification
Delivery ends with proof
Not 'I changed it', but 'I changed these parts, tested these paths, and this risk remains'.