Skip to main content
command CX Codex

flow — Claude Code command: what it does, how to install

The flow command drives a task from idea or bug to ready PR. Works for unattended runs on a ready spec or step-by-step with stops before decisions.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What flow does

flow calls the flow-next-flow skill, which routes work through stages, picks actions and stops where your decision is needed. The command accepts anything — an idea, task ID, branch path, question, bug report.

--auto runs an unattended pass from a ready spec to completion, --tick does one hop. --until=merge goes through gated landing to PR merge. --explain shows the route and reason without writing to .flow/ or dispatching. Without flags the command works in step-by-step mode, offers landing for an existing PR and asks once unless current scoped authorization exists.

Unattended mode ends with a PILOT_VERDICT line. Default unattended flow stops before merge; plain attended flow offers landing for a PR.

What it helps with

  • drive a task from idea to PR without intermediate stops
  • automate a ready spec through to completion
  • stop before an action that requires a decision
  • go through gated landing to merge
  • see the route and its reason before dispatch

Example prompts for the agent

  • flow add email validation to the signup form
  • flow --auto SPEC-42 --until=merge
  • flow --explain fix the duplicate order bug

How to install flow

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/commands/flow.md

Call it with /flow. For all projects use ~/.claude/commands/

Questions about flow

How to install flow in Claude Code?

Run /plugin marketplace add gmickel/flow-next, then /plugin install flow-next@flow-next. The command will appear in .claude/commands/flow.md.

What does the flow command do?

Drives a task through stages — from idea or bug to ready PR. Can work unattended or stop before each decision.

What is the difference between --auto and plain mode?

--auto runs a continuous pass from a ready spec to the end, no stops. Plain mode stops where your decision is needed and offers actions along the way.

Source text

flow.md · MIT
---
name: flow
description: Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a behaviour-keeping cleanup, a design fork, or "what next"; --auto drives a ready spec unattended (--tick for one hop) and ends with a PILOT_VERDICT line; --until=merge continues through scoped gated landing
argument-hint: "[<anything>] [--until=merge] [--explain] [--review=<backend>] | --auto [<spec-id>] [--until=merge] [--tick] [--backlog] [--explain] [--review=<backend>] [--research=grep] [--depth=<level>]"
disable-model-invocation: true
---

# IMPORTANT: This command MUST invoke the skill `flow-next-flow`

The ONLY purpose of this command is to call the `flow-next-flow` skill. You MUST use that skill now.

**Arguments:** $ARGUMENTS

Pass the arguments to the skill verbatim. The skill routes from its shared routing reference, dispatches the existing stage skills, re-evaluates after each hop, and stops at the next human decision. `--explain` prints the route and its reason with no `.flow/` write and no dispatch. `--auto` runs the same route unattended from the ready flag, hop after hop to a terminal (`--tick` for exactly one hop), and ends with one `PILOT_VERDICT` line. `--until=merge` independently selects gated landing through the existing land stage for the selected spec and PR. Default unattended flow stops before merge; plain attended flow offers landing for an existing PR and asks once unless current scoped authorization already exists. The skill's tail reference owns consent, continuation, and recovery.

© Gordon Mickel · MIT · gmickel/flow-next

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set70

The whole set →
chart chart turns one oversized or fuzzy idea into a decision map. Each run settles a single decision and leaves a brief you can capture as a task. CX Codex +1 ★ 730repo stars capture capture synthesizes the active conversation into a flow-next spec at .flow/specs/<spec-id>.md with review checks and overwrite protection. CX Codex +1 ★ 730repo stars tracker-sync tracker-sync projects a flow spec into Linear, GitHub, GitLab, or Jira, then reconciles issue body, status, and comments in both directions. CX Codex +1 ★ 730repo stars flow-next-setup flow-next-setup links a repo to the flow-next plugin: adds versioned docs and config to CLAUDE.md or AGENTS.md. Other agents, such as Codex or Cursor, can then read the same instructions. CX Codex +1 ★ 730repo stars flow-next-prose flow-next-prose — a skill for Claude and Codex that makes the agent read the prose contract in docs/prose.md before a long reply and draft under rules 1–10. CX Codex +1 ★ 730repo stars flow-next flow-next directs AI models to manage fn-N tasks using flowctl instead of markdown TODO lists. CX Codex +1 ★ 730repo stars flow-next-make-pr flow-next-make-pr is a Claude Code skill that builds a briefing from an aid artifact and opens or updates a PR through gh. It detects the spec from the branch and accepts options for draft state, base branch, and dry runs. CX Codex +1 ★ 730repo stars flow-next-worktree-kit flow-next-worktree-kit is a Claude Code skill that creates, switches, and removes git worktrees and copies .env files between them. It supports parallel feature work without switching branches. CX Codex +1 ★ 730repo stars

Project sponsors

Companies that keep this analytics open