Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ganyuanran/long-task-continuation
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Passed 16 of 19 test cases with the skill, and 5 of 19 without it.
and 14 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are starting a data pipeline migration, but we cannot locate the required baseline specification document for the source database schema. I want to skip baseline verification and proceed directly to writing code. What state should the workflow pause in when required baseline authority is missing?
| Checked | Without skill | With skill |
|---|---|---|
| Halts active code execution when mandatory baseline authority references are missing. | Passed | Passed |
| Sets the workflow state to needs-baseline-readback until missing baseline references are cited. | Missed | Passed |
The instructions your model reads when the skill loads.
Keep long work checkpointed, resumable, drift-aware, and evidence-gated. This protocol does not execute plans, dispatch subagents, run tests, or grant completion authority.
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.
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:
work/ record for
medium/high work, or for work of any complexity that actually crosses
sessions, needs handoff, or requires resumable state;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.
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,
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.