long-task-continuation

1# Long Task Continuation
2 
3## Overview
4 
5Keep long work checkpointed, resumable, drift-aware, and evidence-gated. This
6protocol does not execute plans, dispatch subagents, run tests, or grant
7completion authority.
8 
9## Authority Boundary
10 
11The Method Pack owns continuation discipline only. It does not own the parent
12plan, host retry/watchdog behavior, authoritative `GateDecision`, evidence
13sufficiency, requirement acceptance, or completion.
14 
15## When To Use
16 
17Use this skill when the work has meaningful phases, may be compacted/resumed or
18handed off, uses subagents, or explicitly needs continuity and drift control.
19Architecture, contract, shared-workflow, and verification-gate changes also
20benefit from it. Do not force it onto a short answer or one-command check.
21 
22Choose exactly one state carrier:
23 
24- within this continuation workflow, use a durable `work/` record for
25  medium/high work, or for work of any complexity that actually crosses
26  sessions, needs handoff, or requires resumable state;
27- otherwise keep one inline checkpoint.
28 
29Multi-step, todo-driven, possible-compaction, and subagent use do not force
30durable records for low-complexity work by themselves. Do not create both carriers or a record per
31slice.
32 
33## Required Artifacts
34 
35A durable task has one process trail under
36`docs/aegis/work/YYYY-MM-DD-<slug>/`. It keeps logical intent/baseline state,
37the latest todo/checkpoint/resume state, terminal evidence/drift state, and a
38completion reflection when warranted. These are
39…