From flow
Shows current SDLC phase, PR link, elapsed time, next steps, and token usage from .flow-states/<branch>/state.json. Use anytime to check FLOW workflow progress.
npx claudepluginhub benkruger/flowThis skill uses the workspace's default tool permissions.
Show where you are in the FLOW workflow. Reads the state file and
Displays Correctless workflow state: current phase, next steps, time in phase, intensity-based warnings, and setup checks. Invoke via /cstatus anytime.
Generates CTO-level project status from git commits, status, and key files like README, TODOs. Use for standups, 'where are we' queries, or work session starts.
Starts new features: creates Git worktree from prompt-derived branch, upgrades dependencies, opens PR, initializes .flow-states JSON, configures workspace. Use /flow:flow-start <prompt>.
Share bugs, ideas, or general feedback.
Show where you are in the FLOW workflow. Reads the state file and prints a status panel. Read-only — never modifies anything.
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. All local artifacts (logs, plan
files, temp files) are scoped by branch name.
At the very start, output the following banner in your response (not via Bash) inside a fenced code block:
```text
──────────────────────────────────────────────────
FLOW v1.1.0 — flow:flow-status — STARTING
──────────────────────────────────────────────────
```
The status panel includes:
relative_cwd from the state file, shown only when
non-empty. For a mono-repo flow started inside api/, this reads
api. Root-level flows (empty relative_cwd) omit the line.12.4K ($0.087))
computed via window_deltas::flow_total from the per-phase
window_at_* and step_snapshots[] data. The line carries a
trailing ↻ marker when any span observed a rate-limit window
reset. The line is omitted entirely when no phase carries
snapshot data so an empty block does not pollute the panel.${CLAUDE_PLUGIN_ROOT}/bin/flow format-status
Check the exit code:
Exit 0 — stdout contains the panel text (single feature or multiple
features). Print it inside a fenced code block (triple backticks with
text language tag) so it renders as plain monospace text.
Exit 1 — no state file exists. Output the following banner in your response (not via Bash) inside a fenced code block:
```text
No FLOW feature in progress on this branch.
Start one with /flow:flow-start <feature name>.
```
Then stop.