agentleFS
kele-devkele-dev/Claude-Orchestrator-Skill/skills/resume/SKILL.md

resume

Skill10 starsChanged 2 days agoMITView on GitHub

Writes and reads orchestrator checkpoints so long work continues in a new session after a context or rate limit, compaction, or crash. Use on /orchestrator:resume or when on/team/autopilot say to write a checkpoint.

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pause, report and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never write checkpoints inside the repo or a worktree.

    line 16
  2. Distinctive:

    After each team wave when more waves remain.

    line 21
  3. Distinctive:

    After every 3rd autopilot batch.

    line 22
  4. Distinctive:

    Before suggesting a new session for a long conversation.

    line 23
  5. Distinctive:

    After writing a checkpoint because the session is long, or at a stop the user will continue later:

    line 26
  6. Very specific:

    If a tool that starts a new session is available (e.g.

    line 28
  7. Distinctive:

    Write facts in your own words.

    line 43
  8. Very specific:

    No argument: list checkpoints from <store>/checkpoints/ plus legacy <main>/.claude/orchestrator/checkpoints/*.md (legacy ones marked …

    line 46
  9. Very specific:

    No checkpoints found: say so in one line, search no further, and offer to start the task fresh with orchestrator:on.

    line 48
  10. Distinctive:

    Verify cheaply: current branch matches, git log --oneline -5, git status --porcelain.

    line 49
  11. Distinctive:

    If git contradicts the checkpoint, report the mismatch in max 3 lines and ask.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “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

Checkpoints: continue in a new session

Arguments: $ARGUMENTS

<store> is defined in the learn skill (per-project folder under ~/.claude/orchestrator/, same from every git worktree, outside the repo). Use the session-start Orchestrator store: and Checkpoints: lines when present; run the Store command only if they are missing. Every write or delete goes to orchestrator:haiku-coder (TYPE: CREATE, or TYPE: RUN for a delete) with the absolute <store> path.

Location

  • <store>/checkpoints/<slug>.md, slug = kebab-case task name, max 5 words.
  • One file per task, overwritten each time. No history.
  • Never write checkpoints inside the repo or a worktree.
  • Legacy checkpoints are also read (legacy.md in the orchestrator:learn folder; only if legacy files exist); new ones always go to <store>.

When to write

  • At every stop that is not DONE: BLOCKED, DECISION NEEDED, BUDGET, cap or batch limit reached.
  • After each team wave when more waves remain.
  • After every 3rd autopilot batch.
  • Before suggesting a new session for a long conversation.

Hand-off to a new session

After writing a checkpoint because the session is long, or at a stop the user will continue later:

  • Summary, max 5 lines: task, what is done (PASS items, commit, PR), what is open, next step.
  • If a tool that starts a new session is available (e.g. the desktop app's start_session), offer it right away as a card the user starts (fresh context, short title, prompt /orchestrator:resume <slug>); never start it yourself.
  • Otherwise print /orchestrator:resume <slug> in its own code block, to run in a new session.
  • Task DONE (no checkpoint): no card; at most suggest a new session in one line.

Content (max 40 lines)

  • Task: one line.
  • Mode: on / team / autopilot, with its arguments (caps, commit=batch, budget=<N>k, spent <X>k).
  • Branch and last verified commit (or a git diff --stat summary).
  • PRD: path under docs/prd, or a summary of at most 10 lines.
  • Plan table: lane or batch -> files -> PASS / BLOCKED / TODO.
  • Caps used vs allowed.
  • Open decisions or blockers.
  • Next step: exact and actionable.
  • Lessons used: names only.
  • Updated: date.
  • Write facts in your own words. Never include secrets.

Reading (/orchestrator:resume)

  • No argument: list checkpoints from <store>/checkpoints/ plus legacy <main>/.claude/orchestrator/checkpoints/*.md (legacy ones marked "(legacy)"): name, task, updated. Load the only or most recent one if unambiguous, else ask which.
  • With an argument: load the checkpoint with that name; if none matches, treat the argument as keywords and match them against each checkpoint's Task: line (load a single match, else list the candidates and ask).
  • No checkpoints found: say so in one line, search no further, and offer to start the task fresh with orchestrator:on.
  • Verify cheaply: current branch matches, git log --oneline -5, git status --porcelain. Then git fetch -q and git log --oneline <recorded base or last verified commit>..origin/<main branch>: if new commits there touch files the checkpoint names (git diff --stat <that commit> origin/<main branch>), say in max 3 lines which plan items may already be done, and ask before continuing.
  • Trust PASS items unless git contradicts them.
  • Do not re-plan and do not re-read the project. Continue at Next step. If the recorded mode is team or autopilot, those modes are user-invoked only: do not continue in that mode; tell the user in one line to run /orchestrator:team ... or /orchestrator:autopilot ... with the remaining task and caps from the checkpoint. Otherwise continue in on.
  • If git contradicts the checkpoint, report the mismatch in max 3 lines and ask.

Finishing

  • When the task reaches DONE, delete only its checkpoint in <store> with rm "<absolute path>" (RUN may delete only the file named in the brief): as a step in the same haiku-coder brief as the final COMMIT, if one is due, else a lone TYPE: RUN. Say so in the report line.
  • A finished legacy checkpoint: tell the user its path; never delete it yourself.

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.