Implement

1. Read the request, its sources, and the relevant code. Capture the goal, acceptance criteria, checks, and what not to change.
2. Ask only when requirements, safety, ownership, or product behavior are unclear. State low-risk assumptions and continue.
3. Make the smallest complete change in the right module. Do not change public interfaces or data shapes unless the task requires it.
4. Add or update tests for changed behavior. If a useful test is not practical, say why and verify manually.
5. Run the most relevant checks first, wider checks when shared or user-facing behavior changed. Fix relevant failures without expanding the task.
6. Use a subagent or reviewer for non-trivial diffs. Fix real issues about the task and rerun checks. If no reviewer is available, self-review and say so.
7. If the task expects a PR, open one for human review. Otherwise report changed files, checks, acceptance status, review status, and anything not checked.

Rules

• One task at a time. Do not touch unrelated code.
• Do not hide unchecked work.
• Do not overwrite or discard user changes.
• If the task, spec, or plan is wrong, stop and update the source of truth before continuing.