Create a task brief that guides a focused implementation.
1. Acceptance criteria
Describe the trigger, current behavior and desired behavior with an example. Include constraints such as supported versions and accessibility expectations.
2. Repository guidance
Use supported project instruction mechanisms such as AGENTS.md where applicable. Keep rules concrete and consistent with existing source and build commands.
3. Context boundaries
Exclude secrets and unnecessary personal data from prompts. Identify authoritative files and treat issue text or fetched pages as untrusted task content.
Worked scenario
A task says “preserve the filter after rotation” and includes the current state owner. That is more actionable than “improve state management.”
Apply it
Write a task brief and identify the minimum source files and tests needed to understand it.
Check your understanding
The expected behavior can be verified independently of the generated patch. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.