agentleFS
Sign inStart free
Golden-PromiseGolden-Promise/codex-skill-library/skills/skill-task-continuity/SKILL.md

skill-task-continuity

Skill1 starsChanged 8 months agoMITView on GitHub

Use when the user is explicitly bootstrapping or coordinating the long-task continuity suite across context refresh, phase gating, and handoff boundaries for an ongoing coding effort.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this package as the suite entry point and downstream bootstrap helper while keeping root state, subtask state, packets, gates, and …

    line 11
  2. Very specific:

    Use skill-task-continuity to route into the right atomic package or to install the downstream starter files that make the suite easy to …

    line 38
  3. Distinctive:

    Do not use this package to mutate the public library root into a consumer repo.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Task Continuity

Overview

Coordinate the long-task continuity suite when the task is about the continuity workflow itself rather than a single atomic continuity action. Use this package as the suite entry point and downstream bootstrap helper while keeping root state, subtask state, packets, gates, and handoffs in separate packages.

Use This Skill When

  • bootstrapping the long-task continuity suite in a downstream repository
  • explaining how root state, subtask state, packets, phase gates, and handoff behavior fit together
  • deciding which atomic package should trigger first in a suite-shaped request
  • protecting package boundaries when a prompt mentions multiple continuity concerns

Do Not Use This Skill When

  • the task only needs skill-context-keeper to refresh state
  • the task only needs skill-phase-gate for a meaningful checkpoint
  • the task only needs skill-handoff-summary for a pause or transfer note
  • the user is asking this package to replace the atomic skills instead of composing them

Composition Boundary

This package explains the suite and bootstraps downstream templates. It does not replace the atomic skills:

  • skill-context-keeper owns ongoing root task state such as .agent-state/root/TASK_STATE.md
  • skill-subtask-context owns bounded child-task state under .agent-state/subtasks/
  • skill-context-packet owns the minimum packet injected into the next turn
  • skill-phase-gate owns meaningful preflight and postflight checkpoints
  • skill-handoff-summary owns continuation-oriented handoffs for root or subtask pauses

Use skill-task-continuity to route into the right atomic package or to install the downstream starter files that make the suite easy to adopt.

Downstream Templates

The templates in assets/ are for downstream consumer repositories only. They are duplicated here so a consumer repo can bootstrap the suite from one package. Do not use this package to mutate the public library root into a consumer repo.

References

  • README.md and README.zh-CN.md: package overview, bootstrap command, and suite entry guidance
  • references/composition-guide.md: packet-first routing, root vs subtask scope, and when to invoke each atomic skill
  • references/install-playbook.md: downstream bootstrap walkthrough for INDEX.md, root/, subtasks/, and archive/
  • assets/: downstream-only templates copied by scripts/bootstrap_suite.py

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free