Long Task Continuation

If you're orchestrating a task that'll outlive your context window or get handed off mid-flight, this protocol keeps you from losing your place. It's checkpoint-driven: you write intent files, baseline usage snapshots, todo lists, and drift checks to disk under a dated work directory. Before each slice you restate the goal and what you're changing. After each slice you log evidence and update state. The discipline is overkill for quick fixes but essential when subagents are involved, architecture is shifting, or you need to resume three sessions later without guessing where you were. It's not a planner or executor, just the scaffolding that makes long runs legible and recoverable.

GitHub stars: 492
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add ganyuanran/aegis --skill long-task-continuation --agent claude-code

Installs into .claude/skills of the current project.

Files

Long Task Continuation

Overview

Keep long work checkpointed, resumable, drift-aware, and evidence-gated. This protocol does not execute plans, dispatch subagents, run tests, or grant completion authority.

Authority Boundary

The Method Pack owns continuation discipline only. It does not own the parent plan, host retry/watchdog behavior, authoritative GateDecision, evidence sufficiency, requirement acceptance, or completion.

When To Use

Use this skill when the work has meaningful phases, may be compacted/resumed or handed off, uses subagents, or explicitly needs continuity and drift control. Architecture, contract, shared-workflow, and verification-gate changes also benefit from it. Do not force it onto a short answer or one-command check.

Choose exactly one state carrier:

within this continuation workflow, use a durable work/ record for medium/high work, or for work of any complexity that actually crosses sessions, needs handoff, or requires resumable state;
otherwise keep one inline checkpoint.

SKILL.md on GitHub