Commands

Upstream

• /flow-next:strategy: create or update STRATEGY.md
• /flow-next:prospect: generate ranked candidate ideas
• /flow-next:capture: synthesize conversation into a source-tagged spec
• /flow-next:interview: refine a spec through structured questions

Planning and work

• /flow-next:plan: break a spec into dependency-ordered tasks
• /flow-next:plan-review: cross-model review of plan/spec
• /flow-next:work: execute tasks with re-anchored worker agents

Review and PR

• /flow-next:impl-review: cross-model implementation review
• /flow-next:spec-completion-review: verify combined implementation against spec
• /flow-next:make-pr: render PR cognitive aid and open PR
• /flow-next:resolve-pr: resolve PR feedback threads

Maintenance

• /flow-next:audit: review .flow/memory/ against current code
• /flow-next:memory-migrate: lift legacy memory into categorized schema
• /flow-next:prime: assess repo agent-readiness
• /flow-next:ralph-init: scaffold autonomous loop
• /flow-next:sync: plan-sync downstream task specs after drift
• /flow-next:tracker-sync: project a spec to a Linear, GitHub, GitLab, or Jira issue, two-way (Tracker Sync)

Spec ids in commands

Every command that takes a spec or task id accepts either id scheme. The default form is fn-NN (/flow-next:work fn-1, /flow-next:plan fn-1.2). A spec linked to a tracker is referenced by its tracker key instead — /flow-next:work wor-17, /flow-next:plan wor-17, tasks as wor-17.1, case-insensitive. See Spec & task ids.

Recommended paths

Situation	Command path
Conversation already contains the requirement	/flow-next:capture → /flow-next:plan → /flow-next:work
Team needs product clarification	/flow-next:interview --scope=business
Team needs technical clarification	/flow-next:interview --scope=technical --strategy --docs
Plan needs adversarial review	/flow-next:plan-review
Implementation needs review before PR	/flow-next:impl-review
Spec is done and needs final verification	/flow-next:spec-completion-review
PR needs reviewer-focused body	/flow-next:make-pr
PR review comments need resolution	/flow-next:resolve-pr

Most people should not start with flowctl. Slash commands are the product workflow. flowctl is the deterministic state layer those commands call.

Command graph

flowchart LR
  Strategy["strategy/prospect"] --> Capture["capture/interview"]
  Capture --> Plan["plan"]
  Plan --> PlanReview["plan-review (optional)"]
  PlanReview --> Work["work"]
  Work --> Impl["impl-review (optional)"]
  Impl --> Completion["spec-completion-review"]
  Completion --> PR["make-pr"]
  PR --> Resolve["resolve-pr"]

plan produces both the spec (with R-IDs) and the task breakdown. plan-review reviews both before any code is written. impl-review checks code quality on the resulting diff. spec-completion-review is the final gate that confirms every R-ID has evidence in the combined implementation.