flow-reset
Wipe `.flow-states/` on this machine in one pass. PRs, worktrees, and branches are NOT touched — those require per-flow `/flow:flow-abort`.
Best use case
flow-reset is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Wipe `.flow-states/` on this machine in one pass. PRs, worktrees, and branches are NOT touched — those require per-flow `/flow:flow-abort`.
Teams using flow-reset should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flow-reset/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flow-reset Compares
| Feature / Agent | flow-reset | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Wipe `.flow-states/` on this machine in one pass. PRs, worktrees, and branches are NOT touched — those require per-flow `/flow:flow-abort`.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# FLOW Reset
Wipe `.flow-states/` on this machine in one pass. Use when abandoned
features have left orphaned state directories that the per-feature
`/flow:flow-abort` cannot reach. PRs, worktrees, and branches are
NOT touched — those require per-flow `/flow:flow-abort` invoked
against each branch separately before reset.
The skill is a thin wrapper around the `bin/flow reset` subcommand,
which exec's a shell script that resolves the main repo root via
`git rev-parse --git-common-dir` so it works from any cwd in the
repo tree (including linked worktrees) and removes `.flow-states/`
via `rm -rf`.
## Step 1 — Confirm
This is destructive and irreversible — for `.flow-states/` only. PRs,
worktrees, and branches stay untouched. Use AskUserQuestion:
> "Wipe `.flow-states/`? This removes local FLOW state for every flow on this
> machine. PRs, worktrees, and branches are NOT touched. For per-flow GitHub
> cleanup, run `/flow:flow-abort <branch>` separately first."
>
> - **Yes, wipe `.flow-states/`**
> - **No, cancel**
If cancelled, stop.
## Step 2 — Execute
```bash
${CLAUDE_PLUGIN_ROOT}/bin/flow reset
```
If the script exits 0, print:
````markdown
```text
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ FLOW Reset — Complete
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```
````
If the script exits non-zero, surface the stderr to the user so they can
investigate. The script's only failure modes are filesystem errors
(permissions, busy file) and the safety check that refuses to operate at
the filesystem root.
## Rules
- Reset wipes local state only. For each open PR or worktree, run
`/flow:flow-abort <branch>` separately before reset.
- Never rebase, never force push — reset never touches GitHub stateRelated Skills
flow-triage-issue
Triage a single open GitHub issue from a PM lens. Applies a 'Triage In-Progress' label during triage; reads code, checks for already-shipped work, returns a verdict in {close, decompose} with confidence and a flip-condition. Renders and stops — no other side effects.
flow-start
Phase 1: Start — begin a new feature. Creates a worktree, upgrades dependencies, opens a PR, creates .flow-states/<branch>/state.json, and configures the workspace. Usage: /flow:flow-start <feature name words>
flow-skills
Display the FLOW skill catalog grouped by user role. Maintainer and Private buckets render only when invoked inside the FLOW plugin repo.
flow-review
Phase 3: Review — six tenants assessed by four cognitively isolated agents (reviewer, pre-mortem, adversarial, documentation) launched in parallel. Parent session gathers context, triages findings, and fixes.
flow-prime
One-time project setup — configure and commit workspace permissions, install bin/* stubs, and write the version marker. Run once after installing or upgrading FLOW. Usage: /flow:flow-prime
flow-plan
Decompose a problem statement into a pre-planned decomposed issue. Accepts either an issue reference (#N, re-plans in place) or a bare prompt (synthesizes What/Why/AC and files a new issue). Runs a Tech-Lead-default planning conversation, dispatches to PM/Tech Lead/CTO sub-agents on explicit user request, then files or edits the issue ready for /flow:flow-start. Usage: /flow:flow-plan #N or /flow:flow-plan <topic>
flow-orchestrate
Process decomposed issues sequentially overnight via flow-start, tracking outcomes and generating a morning report.
flow-note
Capture a correction or learning to the FLOW state file. Invoke explicitly with /flow:flow-note. Fast — captures and continues without interrupting flow.
flow-learn
Phase 4: Learn — audit rule compliance and identify process gaps. Routes findings to CLAUDE.md, .claude/rules/, and plugin issues.
flow-issues
Group open issues by label into four sections (Blocked, Other, Vanilla, Decomposed) with mechanical sort and a copy-pasteable command per row.
flow-hygiene
Audit instruction corpus health — CLAUDE.md, rules, and memory for staleness, misplacement, duplication, and contradictions.
flow-explore
Open a problem-statement conversation. Stays in discussion mode with PM as default voice; on user signal, files a vanilla What/Why/Acceptance Criteria issue against the current repo. Usage: /flow:flow-explore <topic>