Approval-Checkpoint Long Task
User story
I want long-running work to pause at explicit checkpoints with clear status, next step, and rollback notes, so I can approve or deny risky transitions from in-app or mobile chat without losing context.
Pack contract
Prerequisites and readiness
- Reuses daemon task or goal primitives only
- Chat/mobile approval surfaces are optional but preferred for remote control
- If remote approval channels are unavailable, checkpoints must still work in-app
Inputs and configuration fields
task_kind: task or goalcheckpoint_titles: ordered checkpoint labelsrollback_notes: per-checkpoint rollback instructionssummary_cadence: when to emit status summaries
Outputs and delivery targets
- current checkpoint
- completed checkpoints
- next action
- rollback state / notes
- approval state and recovery guidance
Manual run recipe
- Start daemon task/goal with explicit checkpoint plan in the description.
- Before each risky transition, summarize state and rollback notes.
- Pause for approval.
- Resume only after valid approval resolution.
Example routine wiring
This pack is usually manual or task/goal-backed rather than purely cron-driven; if scheduled, it should only materialize the governed task template, not auto-bypass approvals.
Example prompt
Use the Approval-Checkpoint Long Task pack for this migration. Define checkpoints for backup, schema update, validation, and cutover, with rollback notes and mobile-safe approval summaries.
Failure and recovery behavior
- Stale approval -> reject and request a fresh checkpoint approval.
- Missing remote chat surface -> continue with in-app checkpoint approval.
- Failed checkpoint step -> report rollback notes before any retry.
Verification checklist
- Manual proof pauses and resumes cleanly.
- Checkpoint summaries show current step, next step, and rollback notes.
- Stale approval is rejected cleanly.
- Mobile-safe status output is preserved.
- Pack reuses daemon task/goal runtime, not a side runtime.