maintaining-long-running-task-continuity

Maintains resumable evidence-backed checkpoints for multi-step tasks crossing context or execution boundaries.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill maintaining-long-running-task-continuity-alsdmlals4-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintaining-long-running-task-continuity
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/maintaining-long-running-task-continuity
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill maintaining-long-running-task-continuity-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running tasks often break when they cross response, tool, context, or execution boundaries, losing progress and forcing work to restart. This Skill structures large tasks into verifiable outcome units with resumable checkpoints so interrupted work can resume from evidence instead of re-reading entire conversation history. ## Core Features & Use Cases - Checkpoint Contract: Records objective, completed outcomes, changed artifacts, validation evidence, blockers, protected decisions, and the next exact action in a structured YAML format. - Mode-Based Workflow: Follows an initialize → checkpoint → resume → partial-delivery → close lifecycle to manage task state explicitly. - Partial Delivery: When execution is blocked, delivers completed results first and separates unfinished work, causes, and resume points. - Use Case: During a multi-hour repository migration, the AI checkpoints progress every few tool batches; if the session ends, a new session reads only the latest checkpoint and authoritative sources to resume exactly where work stopped. ## Quick Start Break this large task into verifiable outcome units and maintain a resumable checkpoint after each meaningful step so I can resume if the session is interrupted.

Frequently Asked Questions about maintaining-long-running-task-continuity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an interrupted long-running AI task?

Resume by reading the latest checkpoint and authoritative source documents rather than the full conversation history. The checkpoint records completed outcomes, current state, blockers, and the next exact action needed to continue.

What should a task checkpoint contain?

A checkpoint should record the objective and scope, completed outcomes, changed or created artifacts, validation evidence, current state and blockers, protected decisions, the next exact action, and remaining acceptance criteria.

How often should checkpoints be created during a long task?

Update state, evidence, and next actions every two to three tool batches or at each meaningful stage. This keeps progress recoverable without excessive checkpointing overhead.

What happens when a long-running task gets blocked?

Deliver the completed results first, then separately report the unfinished portions, blocking causes, and resume points. Never mark in-progress work as complete or promise background completion.

When should I not use checkpoint-based task continuity?

Avoid it for short single-step tasks where checkpoint overhead exceeds the work itself. It is designed for multi-step tasks that may cross response, tool, context, or execution boundaries.