Skip to main content
command CX Codex

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

capture synthesizes the active conversation into a flow-next spec at .flow/specs/<spec-id>.md with review checks and overwrite protection.

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 capture does

This command acts as a trigger for the flow-next-capture skill. It disables direct model invocation and forwards all passed arguments straight to the underlying skill.

The skill performs pre-flight verification: it checks for duplicates, inspects evidence completeness after context compaction, and verifies idempotency. It extracts discussion points, marks sources, triggers a review loop for the generated spec, and writes the output through flowctl spec create --plan-file.

Without flowctl and the flow-next-capture skill available in your environment, spec generation will fail at the write step. Accepted parameters include mode:autofix, spec updates via --rewrite <spec-id>, --from-compacted-ok, and --yes.

What it helps with

  • convert current chat context into .flow/specs/<spec-id>.md specification files
  • overwrite an existing specification using --rewrite <spec-id>
  • extract structured evidence from conversation history without manual copy-paste
  • review generated specifications before saving them via flowctl

Example prompts for the agent

  • /capture
  • /capture --rewrite auth-refactor --yes
  • /capture mode:autofix --from-compacted-ok

How to install capture

1Plugin marketplace

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

2Manually: put the files in place

.claude/commands/capture.md

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

Questions about capture

How to install capture in Claude Code?

Run /plugin marketplace add gmickel/flow-next followed by /plugin install flow-next@flow-next. Alternatively, save the command file directly to .claude/commands/capture.md.

What does the capture command do?

It delegates execution to flow-next-capture, turning conversation details into a source-tagged spec file through flowctl.

Which flags can be passed to capture?

You can supply mode:autofix, specify target replacement via --rewrite <spec-id>, bypass compaction warnings with --from-compacted-ok, or auto-confirm with --yes.

Source text

capture.md · MIT
---
name: 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]"
disable-model-invocation: true
---

# 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 --plan-file` write.

© 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 →
map A slash command that hands off to the flow-next-map skill to build a semantic feature index of your repository with clawpatch, provider-free by default. CX Codex +1 ★ 730repo stars memory-migrate memory-migrate — a command for Claude Code and Codex that converts legacy flat memory files (pitfalls.md, conventions.md, decisions.md) into a structured YAML schema with automatic entry classification. CX Codex +1 ★ 730repo stars make-pr This command hands PR preparation to the flow-next-make-pr skill, which renders a PR body and opens it through gh. Choose a draft, base ref, or dry run with flags. CX Codex +1 ★ 730repo stars 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 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 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. 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

Project sponsors

Companies that keep this analytics open