Skip to content
Skills Library
AI & agents · Automation

flow-continue

/flow-continue

Clear the autonomous-flow halt set when the user spoke mid-flow. Invokes `bin/flow clear-halt` so the next assistant turn resumes execution. User-only: the model cannot invoke this skill.

Repository
flow ↗
Licence
MIT
Last repository change
14.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Clear the autonomous-flow halt set when the user spoke mid-flow. Invokes `bin/flow clear-halt` so the next assistant turn resumes execution. User-only: the model cannot invoke this skill.

Original author description

Clear the autonomous-flow halt set when the user spoke mid-flow. Invokes `bin/flow clear-halt` so the next assistant turn resumes execution. User-only: the model cannot invoke this skill.

How it works

  1. Usage
  2. Concurrency
  3. Announce
  4. Step 1 — Detect current branch
  5. Step 2 — Clear the halt
  6. Done
  7. Hard Rules
Original SKILL.md headings · 100 lines, 506 words
SKILL.md preview
---
name: flow-continue
description: "Clear the autonomous-flow halt set when the user spoke mid-flow. Invokes `bin/flow clear-halt` so the next assistant turn resumes execution. User-only: the model cannot invoke this skill."
---

# FLOW Continue

Resume an autonomous flow that paused because the user typed a message
mid-flow. The Stop hook's `check_autonomous_stop` predicate set
`_halt_pending=true` when it observed the user message; this skill
clears that flag so the next assistant turn proceeds. Works universally:
clears any pending halt and acts as a watermark over preceding
conversation, so the autonomous flow resumes whether it was paused by
a user message, a network error, or a rate-limit interrupt.

`/flow:flow-continue` is the ONLY path that clears `_halt_pending`.
The skill is in `USER_ONLY_SKILLS` — the model cannot invoke it, and
`bin/flow clear-halt` independently self-gates by checking the
persisted transcript for the user's slash-command invocation. The
two layers together make the halt durable: nothing the model can do
on its own resumes the flow.

## Usage

```text
/flow:flow-continue
```

No flags, no arguments. The skill takes a single mechanical action.

## Concurrency

This flow is one of potentially many running simultaneously — on this
machine (multiple worktrees) and across machines (multiple engineers).
Your state file (`.flow-states/<branch>/state.json`) is yours alone.
Never read or write another branch's state.

## Announce

Output the following banner in your response (not via Bash) inside a
fenced code block:

````markdown
```text
──────────────────────────────────────────────────
  FLOW v2.7.0 — flow:flow-continue — STARTING
──────────────────────────────────────────────────
```
````

## Step 1 — Detect current branch

Run `git worktree list --porcelain`. The `worktree` entry whose path
matches your current working directory carries a `branch
refs/heads/<name>` line — strip the `refs/heads/` prefix to get the
current branch. Hold the branch name in context for Step 2.

## Step 2 — Clear the halt

```bash
${CLAUDE_PLUGIN_ROOT}/bin/flow clear-halt --branch <branch>
```

Parse the JSON `status`:

- `"ok"` — halt cleared, autonomous execution resumes on the next
  assistant turn. Print "Halt cleared. Resuming."
- `"skipped"` with `"reason":"no_state_file"` — no active flow on
  this branch (state file absent). Nothing to clear. Print
  "No active flow on `<branch>` — nothing to clear."
- `"error"` — print the `message` field verbatim so the user sees
  the failure reason (`unauthorized`, `invalid_branch`,
  `no_transcript_path`, `state_write_failed`). The unauthorized
  branch fires when the most recent real user turn's
  `message.content` does not START with either of the two emission
  shapes Claude Code uses for the slash command — the two-line
  `<command-message>flow:flow-continue</command-message>\n<command-name>/flow:flow-continue</command-name>`
  (Claude Code 2.1.140+) or the legacy
  `<command-name>/flow:flow-continue</command-name>`. The walker
  accepts either via `starts_with` disjunction. A Bash-tool bypass
  attempt this skill makes impossible by definition.

## Done

Output the following banner in your response (not via Bash) inside a
fenced code block:

````markdown
```text
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✓ FLOW v2.7.0 — flow:flow-continue — COMPLETE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```
````

Return to the user. The next assistant turn picks up the paused flow.

## Hard Rules

- Never use Bash to print banners — output them as text in your response
- Never use Bash for file reads — use Glob, Read, and Grep tools instead of ls, cat, head, tail, find, or grep
- Never use `cd <path> && git` — use `git -C <path>` for git commands in other directories
- Never cd before running `bin/flow` — it detects the project root internally

Versions

The database has no other skills named flow-continue.

Database snapshot: 13.11.2026 · package version 9c4371ec26a1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100handoff
    Writes a short handoff note when a session ends mid-task so the next session or person can continue without re-discovery, and resumes from one. Use when asked to hand off, save progress, or continue from a handoff note.
  • 100th-clear
    Hand this session off and continue in a fresh context in the SAME terminal — the th-handoff checkpoint, then `th harness handoff arm`, then the user types `/clear` and `/th-handoff resume <pearl>` (the armed token usually resumes on its own). Invoke as `/th-clear [pearl-id]`.…
  • 84handoff
    Mid-session save-point for /clear-and-resume: a durable handoff file (default) or a copy-paste resume prompt. Use when: 'handoff', 'save state', 'checkpoint this', 'pause', 'come back later', the session is heavy, a context-measuring mechanism says to fork, or responses are…
  • 86handoff
    Write or update a HANDOFF.md so a fresh agent can continue this work. Use when the user says "handoff", "compact this", "context is full", or "/clear and continue".
  • 90repack
    Refresh a long chat — write the next-session handoff, then hand the user /clear → /continue so the work resumes in a fresh context window. Use when the context nudge reaches the handoff level, or the user says "repack", "refresh the chat", "context is getting full", "fresh…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.