task-finish-contract

Task completion with verifiable proof is enforced by requiring explicit GOAL, PROGRESS, and NEXT blocks alongside an EVIDENCE artifact. This structure prevents mid-task stalls by validating that an agent has actually executed the work and produced a verifiable output before closure.

Agents stall mid-task and provide plans without execution due to a lack of enforced state and accountability. By demanding explicit GOAL, PROGRESS, and NEXT declarations plus an EVIDENCE artifact, this mechanism guards against non-execution responses and ensures continuous progress.

The best way to manage task handoffs and re-entry after interruptions is to enforce an explicit completion state using GOAL, PROGRESS, and NEXT sections. This provides clear context recovery and requires an EVIDENCE artifact to confirm exactly what was accomplished before the break.

Requiring an EVIDENCE artifact prevents non-execution in task management by forcing the agent to attach verifiable proof of work. This ensures that declared GOAL and PROGRESS blocks are backed by actual execution, eliminating responses that only offer plans without tangible output.

You need explicit GOAL, PROGRESS, and NEXT blocks for task accountability when handling multi-step tasks, project handoffs, or interrupted workflows. This explicit state tracking ensures every task phase is documented and validated with an EVIDENCE artifact to confirm verifiable closure.

This structured task completion approach is designed for multi-step tasks, handoffs, and projects requiring verifiable closure. Using it for simple single-step requests may add unnecessary overhead, as it mandates GOAL, PROGRESS, NEXT blocks, and an EVIDENCE artifact to confirm completion.