Command
audit
Audit `.flow/memory/` entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry
Development
Command
/capture
Synthesize the current conversation into a flow-next spec at `.flow/specs/<spec-id>.md` — source-tagged, saved-spec review, no silent overwrite
Install
> /plugin marketplace add gmickel/flow-next > /plugin install flow-next@flow-next
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/capture
Context preview
What this command does when you run it.
Synthesize the current conversation into a flow-next spec at `.flow/specs/<spec-id>.md` — source-tagged, saved-spec review, no silent overwrite
Command definition
capture.mdname: capture description: Synthesize the current conversation into a flow-next spec at `.flow/specs/<spec-id>.md` — source-tagged, saved-spec review, no silent overwrite argument-hint: "[mode:autofix] [--rewrite <spec-id>] [--from-compacted-ok] [--yes]"
IMPORTANT: This command MUST invoke the skill `flow-next-capture`
The ONLY purpose of this command is to call the `flow-next-capture` skill. You MUST use that skill now.
**Arguments:** $ARGUMENTS
Pass the arguments to the skill verbatim. The skill handles mode detection (`mode:autofix` token + `--rewrite <id>` + `--from-compacted-ok` + `--yes`), pre-flight checks (duplicate / relevant evidence completeness after compaction / idempotency), conversation evidence extraction, source-tagged synthesis, must-ask cases, saved-spec review loop, and the flowctl `spec create` + `spec set-plan` write.
Ships withflow-next
Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cross-model reviews, receipts. Everything in your repo, zero dependencies. Claude Code · Codex · Cursor · Droid.
Get the whole plugin
Other commands on flow-next.
Command
chart
Decision-map discovery for one oversized/unclear idea before capture - ground, chart a frontier, resolve one decision per invocation, brief for capture
Command
features
Seed or maintain the committed user-POV feature map at `.flow/features/`
Command
flow
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…
Command
impl-review
John Carmack-level implementation review via RepoPrompt or Codex