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.

Multi-step, todo-driven, possible-compaction, and subagent use do not force durable records for low-complexity work by themselves. Do not create both carriers or a record per slice.

Required Artifacts

A durable task has one process trail under docs/aegis/work/YYYY-MM-DD-<slug>/. It keeps logical intent/baseline state, the latest todo/checkpoint/resume state, terminal evidence/drift state, and a completion reflection when warranted. These are TaskIntentDraft, BaselineReadSetHint, BaselineUsageDraft, ImpactStatementDraft, TodoCheckpointDraft, ResumeStateHint, DriftCheckDraft, and EvidenceBundleDraft views, not authoritative runtime records or separate plan owners.

Read only the lifecycle-matched section of durable-work-guidance.md: