recipe-agent-team-worker-checkpoint

Automating worker checkpoints requires a structured workflow that coordinates sync checks, inbox handling, task start or continue operations, artifact writing, and final completion logic. This enforces deterministic task steps and safe transitions between task states.

Orderly task state progression is enforced by requiring the orchestrator to provide RUN_ID, TASK_ID, and AGENT context. The worker recipe then validates artifact requirements and restricts transitions to safe states like done, blocked, or failed.

Handling error states and escalations is managed by prompting for organizer input when needed during the checkpoint flow. This ensures reliable synchronization and prevents manual coordination errors in real-world orchestrations.

To start the checkpoint flow, run the worker recipe by providing the required RUN_ID, TASK_ID, and AGENT context. This initiates the automated sequence of inbox handling, artifact writing, and completion logic.

Triggering the workflow requires the orchestrator to supply RUN_ID, TASK_ID, and AGENT context. Without these specific input parameters, the automated checkpoint sequence and artifact requirement enforcement cannot be applied.

A task gets blocked to enforce safe transitions when artifact requirements are unmet or errors occur during sync checks. The workflow prompts for organizer input to resolve the condition before continuing.