Skip to content

TsukiNi22/ai-utils / skills/ai/pause

Stop everything cleanly in the middle of a task so that it can go on later - no new step started, the step under way brought to a consistent state (never a file half edited or a build left broken), every background job / monitor / subagent / workflow / build / loop / scheduled wake-up started for the task stopped, nothing committed or pushed that the rules of the user do not allow, then a checkpoint written (goal, rules, done, interrupted, the exact next steps, what was stopped and how to start it again, files changed, decisions) and one short message - the work resumes at the next "continue" (continue-work). Use whenever the user says /pause, "stop tout proprement", "arrête-toi proprement", "mets en pause", "on reprendra plus tard", "stop et reprends au prochain continue", "pause the work", "stop cleanly".

FileKindSize
SKILL.mdskill md4.6 KB
requires.txtmarkdown14 B
scripts/checkpoint.shexecutablescript2.3 KB
templates/checkpoint.mdmarkdown968 B

templates/checkpoint.md

View on GitHub
# Paused: {{TASK}}

**Project**: {{PROJECT}} · **Paused**: {{DATE}} · **Branch**: {{BRANCH}} @ {{COMMIT}}

## Goal
- {{what the user asked, their words kept for the parts that matter}}

## Rules of the user for this task
- {{git: commit / push or not, language, style skills, what needs a confirmation}}

## Done
- {{step}}: {{result, verified how}}

## Interrupted
- {{the step under way when the pause came}}: {{exact state - finished / half done (what is applied, what is not) / not started}}

## Next (in order)
1. {{the first thing to do on `continue`: the command or the edit, with paths}}
2. {{...}}

## Stopped
- {{background job / monitor / agent / build / loop stopped}}: {{how to start it again, or "not needed any more"}}

## State of the files
- Changed, not committed: {{paths}}
- Created for the task (temp, scratch): {{paths, to keep or remove at the end}}

## Decisions and open points
- {{choice made}}: {{why}}
- {{question for the user, if any}}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall