Call this before starting meaningful work. Defines the task contract: goal, non-goals, and explicit done criteria that later tools use to detect scope drift and verify completion.

Call this when breaking a task into measurable implementation or research steps. Checkpoints make progress auditable instead of relying on vague status updates.

Call this after starting, completing, or intentionally skipping a checkpoint. Attach evidence such as test output, files, or notes whenever possible.

Call this when choosing an implementation approach, rejecting an alternative, or deciding whether a requested change is in scope. Records rationale for later review.

Call this before doing adjacent cleanup, broad refactors, extra features, or work that may not map to the recorded goal. It warns when the proposed action appears outside the task contract.

Call this whenever you have proof of progress: tests, typecheck, lint, review, manual verification, artifacts, paths, or URLs. Link evidence to done criteria when possible.

Call this when a done criterion becomes met, not met, pending, or explicitly waived. In strict verification, met criteria should have linked evidence.

Call this when progress is blocked by missing input, failing dependencies, permissions, unclear requirements, or external failures.

Call this when a blocker is resolved or waived. Open blockers prevent taskguard_verify_done from returning ready.

Call this before final response, commit, PR, or handoff. It checks done criteria, checkpoints, blockers, and optional evidence requirements so the agent does not falsely claim completion.

Call this when resuming work or when the user asks what remains. Returns the active task ledger or a specific session.

Call this only when the user abandons, restarts, archives, or deletes a TaskGuard session. Prefer archive over delete to preserve audit history.