Task Execution Simple

Implement the supplied scope and leave a verified, recoverable result.

Work independently

1. Read repository instructions, the supplied task or spec, relevant code and tests, and current version-control state.
2. Confirm the task is implementable from repository evidence. Stop before editing only when a missing behavioral boundary, technical choice, or execution-order decision would materially change the result. Name the missing decision and why current evidence does not decide it so the user can resolve it directly or capture it in a suitable artifact.
3. Before editing, state a concise approach preview: the change surface, core strategy, material constraints, and verification seam. Do not create a formal artifact for straightforward work.
4. Choose isolation before editing. Reuse suitable existing isolation. Create a branch or worktree for non-trivial work on a default or shared branch, possible collision with existing dirty changes, parallel work, or likely cross-session execution. Stay in place for a small safe change or explicit user direction.
5. Implement only the supplied scope. Preserve unrelated user changes.
6. Run the most relevant practical verification, complete the implementation-review correction loop, and inspect the resulting diff.
7. Update existing docs or task state when implementation changes their stated facts or when requested.
8. Before advancing to another task or waypoint, create a cohesive Git checkpoint for stable scoped changes when repository policy and user direction permit routine commits. Include task documents whose truth changed.
9. If a checkpoint is intentionally unavailable, report the exact reason and uncommitted surface instead of silently continuing with completed work.
10. Report result, verification, residual risk, commit or uncommitted state, and any closing action still awaiting confirmation.

Finish only when acceptance is satisfied, final verification reflects current code, review findings are resolved, and stable changes are committed or explicitly accounted for. Do not require another local skill, docs layout, tracker, branch convention, fixed commit sequence, or review pause.