resume
Skill0 starsChanged 2 days agoMITView on GitHub
Resume a keyturn task that stopped (usage limit, closed session, crash, a question to the client, the rework limit) from its state file, keyturn/internal/state/<task>.md on the branch task/<task>, in a new session, on another machine, or with another AI tool. With no task named, lists the tasks that can be resumed from every local and remote task branch. Checks the state file with a script first and stops on any problem instead of guessing; never continues past an unanswered decision card or before a usage limit resets.
64 other projects use a version of this.
Adopted by
Most recently taken up by
- theraihanrakibb/agent-skillstheir own version, first seen Nov 16, 2026
- DeepExtrema/Tesseracttheir own version, first seen Nov 16, 2026
- kele-dev/Claude-Orchestrator-Skilltheir own version, first seen Nov 16, 2026
- netarz/gisoo-skills-registrytheir own version, first seen Nov 15, 2026
- kuldeep-jadeja/claude-handoff-plugintheir own version, first seen Nov 15, 2026
- gutohuida/AgentWeavetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pause, status and 10 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.
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 7 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 15 projects that use this
MicrosoftSkillreport
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
MicrosoftSkillconfig
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
sahinSkillexecute
Also in 4 projects that use this
u9401066Skillbug-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
- +2 more from microsoft
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- H-mmer/pentest-agents★ 815same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- qbeka/jev-job-search★ 368same name
- thesun4sky/jobstack★ 216same name
- EmeaAppGbb/spec2cloud★ 100same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- thiagofinch/mega-brain★ 95same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- junjiezhou1122/ideascientist-claude-code★ 35same name
- wrg32786/aigent-os★ 26same name
54 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- conventionsSkill
- designSkill
- implementSkill
- localizeSkill
- project-configSkill
- qaSkill
- reviewSkill
- security-reviewSkill
- specSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 6 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
No answer is not consent: Do not continue past a decision card or requirements the client has not answered, not even with the card's …
- Distinctive: line 17
Not before the reset: Do not continue a task stopped for a usage limit before the time it records.
- Distinctive: line 18
Never discard work: Do not reset, stash, or overwrite uncommitted changes or a branch that has diverged.
- Very specific: line 51
Run task_state.py list --task <task>.
- Distinctive: line 57
Run git status --porcelain.
- Very specific: line 58
Run git switch task/<task> (this creates the local branch from the remote one when only the remote one exists).
- Very specific: line 62
Use the lines list printed.
- Very specific: line 84
Leave the steps table as it is, including the current step's row when it says in progress: the step is rerun from its start in step 6, and …
- Very specific: line 89
Run task_state.py check keyturn/internal/state/<task>.md until it prints ok.
- Distinctive: line 101
No Git repository: stop and report it; tasks are found only from their branches.
- Distinctive: line 103
A task branch without a state file: stop and report it (step 3).
- Very specific: line 106
No
deliverskill: stop before recording the resume (step 4).
“Common” is measured: kept by at least 6 in 10 of the 56 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.
Files
resume
Continue a stopped task from the step where it stopped, using only what is in the repository. Everything this skill needs is in this file, the script next to it, and the files it names. For background, see keyturn's docs/design/resuming-work.md and ADRs 0009 and 0011; the procedure does not depend on them.
Paths below that start with scripts/, ../, or ../../ are relative to the folder of this SKILL.md file. Paths that start with keyturn/ are in the project's repository.
Rules
- Never guess where to continue. The state file decides. If the script reports any problem, stop and report every problem; do not work out the step from the documents, the commits, or the conversation.
- Never rely on the previous session. A step that was stopped in the middle is rerun from its start, from its inputs (the documents and commits on the task branch). Nothing the earlier session was thinking or had not committed counts.
- No answer is not consent. Do not continue past a decision card or requirements the client has not answered, not even with the card's recommendation. Work that depends on the answer waits.
- Not before the reset. Do not continue a task stopped for a usage limit before the time it records; say when it can continue.
- Never discard work. Do not reset, stash, or overwrite uncommitted changes or a branch that has diverged; stop and ask.
Inputs
- Optional: the name of the task to resume (for example,
delivery-1). Without it, list the tasks that can be resumed. - The project's Git repository, with its task branches
task/<task>(local, or on a remote). ../../templates/internal/state.md: the fields and values of a state file. The script reads it; you need it only to edit the state file in step 5.- For a task waiting for the client: the decision card or
keyturn/client/approvals.mdnamed in its "Open questions", and the scripts../spec/scripts/approval.pyand../project-config/scripts/project_config.py. - To continue: the
deliverskill,../deliver/SKILL.md.
Outputs
- With no task: the list of tasks that can be resumed, for the person who asked.
- With a task: the state file, updated for the resume and committed on the task branch, and the task continued from its step. Or, when it cannot continue, a short message saying why and, if known, when it can.
Procedure
The helper script scripts/task_state.py checks state files and lists task branches. It needs Python 3.9 or later and Git, and uses only the standard library. Run it from inside the project's repository; below, task_state.py means its full path.
task_state.py list [--task <task>]checks the state file on everytask/<task>branch, local and remote, without checking anything out. For each task that is not done (with--task, for that task even when it is done) it prints<task> (<branch>):and, indented, its status, current step (with that step's status in the steps table), why it stopped, and when it can continue.task_state.py check <file>checks one file and printsokand the same lines.- Both print every problem on its own line,
error: <where>: <problem>(inlist, indented under the task's heading), and then exit 1. In the fulllist, exit 1 means that some task has problems; the tasks without problems are still listed. The check never depends on the clock: the same file always gives the same verdict and the same problems.--now YYYY-MM-DDTHH:MMZ(default: the current UTC time) only decides whether a reset time has passed.
1. Bring the branches up to date
Run git remote. If it prints nothing, there is no remote: only this machine's task branches can be seen, so say so when you report. Otherwise run git fetch --all --prune. If that fails (for example, no network), say that tasks pushed from another machine may be missing or out of date, and go on with what is there.
2. With no task named: list the tasks, then stop
Run task_state.py list. Tell the person, in their language, which tasks can continue now, which are waiting and for what, and which have problems (the error: lines under a task's heading), and that done tasks are left out. Ask which one to resume, and stop. If it prints no tasks to resume, say so; a new task is started with the deliver skill.
3. With a task named: check it and check out its branch
- Run
task_state.py list --task <task>. Look only at this output; other tasks do not matter here.- Any
error:line (indented under the task's heading): stop. Show the person every line, and say the task cannot be resumed until they are fixed. Do not fix the state file by guessing: it is fixed by hand, to what the task branch shows, by someone who can tell, and checked again. The lines you may see besides problems in the file itself:error: task/<task>: has no local or remote branch: there is no such task.error: task/<task>: should not have diverged: <branches>; ...: the local and remote branches both have commits the other lacks. Ask the person how to merge them.error: <branch>:keyturn/internal/state/<task>.md: is missing: where the task stopped cannot be told; do not work it out from the outputs.
status: done: there is nothing to resume. Say so, and stop.
- Any
- Run
git status --porcelain. If it prints anything, stop and ask the person what to do with those changes; never discard them. - Run
git switch task/<task>(this creates the local branch from the remote one when only the remote one exists). Iflistprintednote: task/<task> is behind <remote>/task/<task>; fast-forward it before resuming, rungit merge --ff-only <remote>/task/<task>.
4. Decide whether it can continue now
Use the lines list printed.
status: running: the session that ran it ended without recording a stop (a crash or a closed terminal), or it is still running somewhere else. Ask the person who asked you to resume it to confirm that no other session is working on this task, and go on only after they confirm. Their confirmation is recorded in the History line in step 5.- Then
can continue::now, ornot applicablewith statusrunning: go on.after <time>: if the line ends withnot yet (now ...), stop and tell the person the task can continue after<time>(UTC). If it ends withthe time has passed, go on. This skill does not check the current usage itself;deliverchecks it before it starts each step and stops again if the limit is still near.when the client approves: requirements version <n>: only once the client's answer is recordedorwhen the client answers: decision card <n>: only once the client's answer is recorded: check whether the client has answered, as below. If they have, go on. If not, only the work that depends on the answer waits: the "Blocks:" part of that item in "Open questions" says which steps. If it blocks the current step (for example, "design and every later step" when the current step is design), stop and say what is waiting for the client. If it does not, go on: the item stays in "Open questions", anddeliverstops again before a step it blocks.when the maintainer decides: <what>: only once the maintainer has decided: stop and ask the maintainer. Go on only after they have decided, and follow their decision.
- Whatever "Can continue" says, do not run the current step while any unanswered item in "Open questions" lists it under "Blocks:".
How to tell whether the client has answered:
- Requirements version
<n>: runproject_config.py get english_onlyand, if it printstrue,project_config.py get client_language. Then runapproval.py status, adding--lang <client_language>whenenglish_onlyistrue. The client has approved only if its first line isversion <n>: current, answer: <answer>with that same<n>, and<answer>is exactlyapproved(or, whenapprovals.mdis written in another language, that one word in its language) and nothing else.waiting, an empty answer, "not approved", and an approval with conditions are not approvals. If the only errors it prints are about the kept copy of the translation, the approval still counts; tell the person, because thespecskill needs to know. When you are unsure what an answer means, ask whoever runsspec; do not decide it. - Decision card
<n>: open the card linked in "Open questions". The client has answered only if itsStatus:line isansweredand, under "Your answer", theAnswer:andDate:lines are filled in: not empty, and no longer the template's text in angle brackets (<option, and any comment>,<YYYY-MM-DD>). - Before writing anything, check that the
deliverskill (../deliver/SKILL.md) is available. If it is not, stop and report it:resumedoes not run the pipeline itself, and recording a resume that nothing runs would leave the task markedrunning.
5. Record the resume
Edit keyturn/internal/state/<task>.md, keeping to the fields and values of ../../templates/internal/state.md:
Status: running,Stopped because: none,Can continue: not applicable.Updated:the current UTC time, rounded down to the minute, in the formYYYY-MM-DDTHH:MMZ. Take it once (for example, withdate -u +%Y-%m-%dT%H:%MZ) and use the same time in the History line below; if you pass--nowto the script, pass that time too.- Leave the steps table as it is, including the current step's row when it says
in progress: the step is rerun from its start in step 6, anddeliverupdates the row when it runs it. - In "Open questions", remove the items that were answered or approved, and keep the ones still waiting; write
None.when nothing is left. - In "Summary", say in one or two lines that the task was resumed, naming the step by its name in the steps table (for example, "Resumed in the implement step after the usage limit reset."). Like the whole state file, it is written in English, in plain words (the template asks for lines a client could follow).
- In "History", add one line at the end, and never change the earlier lines:
- <time>: resumed: in <step>, from commit `<hash>`, where<hash>is the short hash thatgit rev-parse --short HEADprints before you commit (usually 7 characters). The check does not read hashes in History; in the steps table it accepts 7 to 40 hexadecimal characters in backticks. For a task that wasrunning, add(the earlier session ended without recording a stop; confirmed that no other session runs it).
Run task_state.py check keyturn/internal/state/<task>.md until it prints ok. Commit only that file on the task branch, with the message chore(state): resume <task> in <step> (for example, chore(state): resume delivery-1 in implement).
6. Continue from the step
The step to continue is the current step. Each step in the steps table is named after the keyturn skill that runs it: spec, design, conventions, implement, qa, security-review, review, and deliver (the last step, which writes the acceptance guide and the delivery report).
- Whether the step's row says
in progress(it stopped in the middle) ornot started, run the step from its start, from its inputs. Its earlier partial outputs are written again, not continued. - Steps marked
doneorskippedare not run again. - Continue with the
deliverskill from that step: follow its procedure from that step on.deliverruns the steps and the gates between them, and keeps the state file current at every step boundary and when the task stops again.
When inputs are missing
- No Git repository: stop and report it; tasks are found only from their branches.
- No task branches: say there are no tasks to resume.
- A task branch without a state file: stop and report it (step 3).
- No template (the script reports that
../../templates/internal/state.mdcannot be read): stop and report it; the file cannot be checked without it. - A decision card or
approvals.mdnamed in the state file is missing: stop and report it; the client's answer cannot be confirmed. - No
deliverskill: stop before recording the resume (step 4).
Notes
- The script reads the allowed fields, values, sections, and steps from the template at every run. If the template changes in a way the script does not understand, the script reports it; update the script and its tests with the template.
- Besides the format, the check makes sure the file says where to continue without a guess: the title and
Branch:name the task, the current step is the first step that is neither done nor skipped, a stopped task says why, a usage-limit stop says when the limit resets, and a task waiting for the client lists what it waits for in "Open questions", where "Blocks:" names only steps of the template (or "every later step" right after one) and requirements (R-n). - The check does not look up commit hashes in Git: a hash in the steps table or History must have the right form, but is not checked to exist.
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
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.

