Task State

Maintain a checkpoint, not a process log.

Update the task

1. Find the repository's existing issue, task file, checklist, roadmap entry, or other state convention.
2. Update it in place. If none exists and a durable checkpoint is useful, propose the smallest repository-consistent Markdown record.
3. Use acceptance checkboxes as the primary progress record and set planned, in-progress, blocked, or completed from the definitions below.
4. Add only the state required by the current branch:
   • while work continues: update satisfied acceptance;
   • when stopping or handing off: add a recovery checkpoint only for context another session cannot readily reconstruct;
   • when blocked: record the blocker;
   • when completing: replace transient recovery state with one final verification summary.
5. Report any mismatch among status, acceptance, blocker, and final verification.

Finish when the artifact states the current truth without preserving routine activity. Use references/task-state-template.md only when no local format fits. Require no docs directory, labels, branch scheme, or fixed transition sequence.

With milestone context, update only the selected task and return its result or blocker to the workflow; milestone placement, discovered-work routing, and closure remain workflow-owned.