long-task-continuation
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Install / Use
npx skills add GanyuanRan/Aegis --skill long-task-continuationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of long-task-continuation
long-task-continuation scores 85/100 on our quality scale, 2651st of 4,698 Development & Engineering skills we index.
Its SKILL.md is 9.2 KB long, well organised into 12 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,273 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so long-task-continuation is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
long-task-continuation compared with similar skills
All 4 of these similar skills score higher than long-task-continuation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| long-task-continuation (this skill)by GanyuanRan | 85 | 1.3k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install long-task-continuation?
- Run
npx skills add GanyuanRan/Aegis --skill long-task-continuation. The install tabs above show the steps for each supported agent. - Which AI agents does long-task-continuation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is long-task-continuation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is long-task-continuation still maintained?
- The repository was last updated about 2 months ago, so long-task-continuation is actively maintained.
Skill content
View source on GitHubname: long-task-continuation description: "Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion."
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:
- use a durable
work/record for medium+ work 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 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:
## Required Artifact Layoutand## Create A Durable Work Recordfor a new durable work record;## Update A Slicewhen an existing helper-backed record needs sidecar updates;## Retry Convergence Detailfor retry/attempt bookkeeping;## Pause, Handoff, And Completion Bundlewhen preparing a pause, handoff, or completion bundle; and## Expanded State Fieldsonly when natural checkpoint prose is ambiguous.
The reference owns artifact layout and <aegis-workspace-helper> command
detail; this file owns carrier selection, resume order, drift decisions, and
stop conditions.
An Execution Readiness View may be kept in the intent or active checkpoint
for medium/high, handoff-prone, long-running, subagent-driven, architecture,
contract, compatibility, or retirement-sensitive work. It renders existing
intent, scope, baseline, owner, test, review, and drift constraints; it is not a
new JSON artifact or completion authority.
Planless Slice Lane:
- When an existing parent plan/spec owns a bounded task, reuse it and the current checkpoint. For a no-parent direct bounded request with no new durable or unclear verification boundary, use an inline checkpoint.
- State one compact
Slice Card: Goal,Parent plan/spec(ornone — direct bounded request), Files, Boundary, Verification, and Stop. - The slice goal closes only that slice. Final completion returns to the parent
or direct bounded request through
verification-before-completion. - Do not create a plan/spec merely to give a micro-slice a parent, and do not create per-slice plans/specs or work records.
- Escalate when a new owner, contract, schema, public API, architecture, migration, persistence, security/permission, distribution/release surface, unclear verification boundary, or mismatch with parent scope or acceptance appears.
When durable architecture decisions are in scope, these work records are the preferred ADR Auto Backfill source. Preserve decision signals, source refs, alternatives, compatibility, retirement, drift, and baseline-sync questions.
Start Protocol
Before execution:
- Capture requested outcome, scope, non-goals, risks, parent plan/goal, success
evidence, and stop states (
done | blocked | needs-verification | scope-exceeded). - Identify required baseline refs and record acknowledged, cited, and missing
refs. Missing authority pauses in
needs-baseline-readback. - Choose inline or durable state once, then record the todo map, active slice, completed slices/evidence, blockers, next step, and current branch/HEAD.
- When an
Execution Readiness Viewexists, retain its intent lock, scope fence, baseline lock, compatibility/retirement boundary, tests, reviews, evidence, and rewind rules. - For a new helper-backed record, use
durable-work-guidance.mdto create and structurally check it before implementation.
Retry Convergence Protocol
A failed verification is another attempt in the current slice, not a new
slice. Keep failed-attempt telemetry out of terminal evidence and normal
commits. Only evidence-finalized, blocked, or abandoned is terminal.
When retry state reaches process-artifact-pressure, stop auto-retry and route
to systematic-debugging or verification-before-completion. Load the durable
reference only when the attempt/evidence commands or sidecar rules are needed.
Per-Slice Protocol
Before each slice, state the current goal/todo, intended edits, explicit non-edits, verification, and readiness alignment. A bounded parent-plan or no-parent slice uses the compact Slice Card rather than a new plan/spec.
After each slice, update completed todos, evidence refs, newly used baseline
refs, blockers, next step, and drift decision. When an active helper-backed work record exists, read durable-work-guidance.md and update that same record;
never create another workstream for bookkeeping.
When patch-shape/ripple triage, an H-class finding, or a bounded compatibility
mitigation fired, a locally green result does not clear the direction. Retain
PatchShape, CanonicalOwner, UpwardDrillSignal, latest outcome, and one
bounded evidence ref; do not copy raw logs or full diffs. If no fresh evidence
exists, the state is needs-verification or partial.
Resume Protocol
Resume in this order:
- Read original intent, parent plan/goal, latest checkpoint and resume hint.
- Re-read required baseline refs and relevant active
CONTEXT.mdlanguage. - Read the
Execution Readiness Viewwhen present. - Compare checkpoint branch/HEAD, completed commits, evidence refs, and claims
with the current worktree.
Treat inherited completion claims as unverified until the worktree confirms
them. Correct contradictions in the checkpoint, disclose them in the final
report, and do not republish stale claims as current.
Preserve the claim's subject, scope and resume-time state; distinguish that
from later repair and from historical execution you cannot verify. One
accurate correction may cover related claims. The record must adopt it,
without elsewhere denying it or assigning it to another scope. A reviewer's
classification is contestable: if material disagreement remains unresolved
after checking evidence, retain
needs-verificationwithout forcing assent. If evidence resolves it, retain the supported conclusion and verify normally. - Compare the active slice against intent lock, scope fence, baseline lock, compatibility/retirement boundary, tests, reviews, and non-goals.
- Re-run the drift decision, then name the next smallest authorized action.
Any disagreement among plan, checkpoint, baseline, context, readiness view, or
worktree pauses execution. A semantic conflict routes to
establishing-project-context; an unplanned repair re-reads the retained
invariant, owner seam, patch shape, and causal topology, then route comparison to
systematic-debugging. A new carrier name alone does not prove a new direction. Never resume from memory alone.
Drift Check
Check original intent and stop condition, parent scope/acceptance, compatibility,
new owners/fallbacks/adapters/branches, retirement, evidence freshness, and any
readiness locks. Allowed decisions are continue, pause-for-user,
needs-baseline-readback, needs-verification, and blocked.
Never emit gate-passed, completion-granted, or authoritatively-safe.
Completion Candidate Protocol
Before a completion claim:
- Use
aegis:verification-before-completion. - Confirm every todo has status, blockers are resolved/externalized, evidence covers acceptance, and drift has no blocking state.
- If a durable record exists, load
durable-work-guidance.mdfor the completion bundle and structural workspace check. - For durable architecture work, pass the work record, proof bundle and ADR signals to verification for ADR Backfill Check.
Generated packs are future-runtime inputs only. Method Pack output remains verified evidence and advisory judgment, not authoritative completion.
Minimal Reporting Shape
Report naturally and omit empty structures. Keep these semantic slots visible:
Aegis Visibility; current todo/active/completed/next; baseline usage decision;
readiness state when present; fresh evidence; inherited-claim corrections when
a resumed record overstated its state; retry/convergence state when
relevant; drift decision; risk/unknown; and the next smallest safe action.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
