checkpoint-approval

Checkpoint-approval enforces mandatory user approval at critical workflow transitions by presenting plans or changes and waiting indefinitely for explicit consent. It prevents accidental progression by requiring affirmative input like 'approved' or 'proceed' before transitioning the task to the next state.

Yes. Checkpoint-approval blocks progression until explicit user approval is received. It creates an audit trail via flag files and only transitions the task state after approval and flag creation, ensuring human oversight prevents bypass.

After the SYNTHESIS phase, invoke checkpoint-approval with the plan file and task name. It presents the plan in structured format, waits indefinitely for explicit approval, creates a persistent flag upon consent, and transitions to IMPLEMENTATION only after approval is secured.

Checkpoint-approval integrates human-in-the-loop control by halting workflows at critical checkpoints, presenting synthesized output clearly, and requiring explicit user consent before state transitions. This satisfies compliance requirements and prevents unintended consequences from silent progression.

Yes. Upon receiving explicit approval, checkpoint-approval creates persistent flag files (user-approved-synthesis.flag or user-approved-changes.flag) that serve as an audit trail, documenting when and that user approval was granted before state transitions.

Use checkpoint-approval for high-risk transitions requiring explicit consent—plan approvals, change merges, or compliance checkpoints. Avoid it for low-risk autonomous tasks where user oversight isn't mandatory or where indefinite waiting would block necessary automation.