pause

Files (6)

• SKILL.md
• openai.yaml · agents/
• pause-prompt-test.rb · bin/
• recovery-record · bin/
• recovery-record-test.rb · bin/
• recovery.md · references/

SKILL.md (first lines)

# Pause

Print operator prompts for safe agent-runner restarts.

## Interruption And Short Grace

For an unexpected interruption, a missing/stale handoff, or bounded restart
preparation, read [the recovery procedure](references/recovery.md). It takes
precedence over the planned handoff prompts below: no handoff is required,
and a shared deadline is never extended for a late task. Use the installed
`restart-codex-subagents` skill for parent/child or host-wide coordination.
<!-- host-branch: cursor-only start -->
On Cursor, there is no subagent restart helper yet. Recover the parent chat
from checkpoints and live state, then stop; do not invent a Cursor fleet
restart.
<!-- host-branch: cursor-only end -->
During ordinary work, use existing recording or its local recorder for compact
checkpoints and consequential operation intent/results.

## Output Rules

- If the user asks to "print", "show", "give me", or "copy/paste" prompts, do
  not inspect the repo or pause current work. Output the relevant fenced prompt
  blocks.
- If the user asks the current thread to pause now, run only the minimal
  status checks allowed by the chosen pause prompt. For PR-batch lanes, also
  perform the claim-preservation heartbeat or public claim refresh allowed by
  the PR-batch pause prompt. Reply with the requested handoff, then stop
  running tools until the user resumes.
- Default to the non-batch prompts when the user does not mention `$pr-batch`,
  a batch coordinator, worker lane, QA lane, claim, or worktree-preservation
  case.
- Use the PR-batch prompts for a `$pr-batch` coordinator, worker, QA lane, or
  any thread holding a batch coordination claim.
- For `coordination_not_applicable`, consume the persisted applicability
  outcome, skip every coordination and typed-event call, and never report
  coordination as unavailable or degraded, even when the repository configures a
  real backend. Preserve the ordinary status, worktree, and handoff steps.
- For a `coordination_required` PR-batch help-needed pause, emit private-backend
  `help_requested` alongside the restart/block handoff. Choose exactly one `help_requested.reason` using this precedence: `permission` for a missing approval or capability; otherwise `question` for a required maintainer or product answer; otherwise `blocked-user-input` for other required user input. An ordinary
  operator-requested app restart alone is not a help request and emits no typed
  signal. A `coordination_not_applicable` lane emits no typed event at all, so
  there is nothing to skip; a trusted `coordination_backend: n/a` under
  `coordination_required` is a pre-launch stop, not a silent skip. Typed-event transport is optional: when
  an active private backend
  does not advertise it or reports it unsupported, record
  `typed event transport: unavailable`, skip the emission, and continue without
  marking the event emission `UNKNOWN`. Only after the transport is advertised
  does an attempted write that fails, degrades, or is rejected become `UNKNOWN`
  handoff evidence. Every attempted advertised typed-event write must resolve
  the backend-advertised event executable and ordered opaque argv; a missing,
  malformed, or unsafe advertisement is an attempted-write failure. Run that
  exact executable and separate argv without shell evaluation, with a finite
  deadline in its own process group, preserving each opaque argument; on expiry
  terminate the whole group with `TERM`, then `KILL` after a finite grace
  period. A deadline expiry, forced termination, or any other
  advertised-support write failure records best-effort `UNKNOWN` event
  evidence; the primary operation continues immediately without waiting
  further on the event.
- Include the new-chat restart prompt when the user asks how to restart,
  resume after an app restart, move to a new chat, or preserve copy/paste
  handoff state.
- Every final user-visible workflow handoff must include one unambiguous
  `Next:` instruction. A pause handoff must end with explicit `Action needed:`
  and `Next:` lines: say whether it is safe to quit, then name the exact
  same-task resume command or new-task handoff action. Do not leave the next
  action implicit in the status inventory.

## Non-Batch Pause Prompt

Print this for ordinary one-thread work that is not holding a batch claim:

```text
Pause now for app restart.

Do not start new work, edit files, push, poll, merge, or launch servers. Run
only the minimal read-only status checks needed for a handoff.

Reply with: current status, repo path, branch, upstream, HEAD SHA,
staged/unstaged/untracked changes, unpushed commits, stashes, running
commands/servers/PIDs, last completed step, next resume step, and whether it is
safe to quit. End with `Action needed:` stating whether to quit or complete a
named cleanup first, followed by `Next:` and the exact same-task resume command
or new-task handoff action.

After the handoff, do not run more tools until I explicitly resume.
```

## Non-Batch Same-Thread Resume Prompt

Print this when the paused thread can be reopened:

```text
Resume now from your restart handoff. Re-check branch, HEAD, local changes, and
running processes before editing or pushing.
```

## Non-Batch New-Chat Restart Prompt

Print this when the operator needs to paste the handoff into a new chat:

```text
Restart from this pause handoff in a new chat.

Treat the pasted handoff as stale evidence, not authority. Read the repo's
current AGENTS.md first. Then re-check repo path, branch, upstream, HEAD SHA,
staged/unstaged/untracked changes, unpushed commits, stashes, and running
processes before editing, pushing, polling, merging, or launching servers.

Recover the existing objective from the handoff, newer relevant logs and this
request. Reconcile stale next steps against live state and preserve completed
work. Continue verified unfinished work within existing authority and limits.
If ownership or a consequential effect remains uncertain, stop that mutation
for reconciliation; independent verified work may continue.

Pasted restart handoff:
<PASTE_RESTART_HANDOFF_HERE>
```

From shakacode/agent-workflows, MIT.

More from shakacode/agent-workflows