When to Use

You know what to build

Use /flow-next:capture if the requirement is in the current conversation, then plan the generated spec.

/flow-next:capture
/flow-next:plan fn-1
/flow-next:work fn-1

You have a conversation, not a spec

Use /flow-next:capture. It synthesizes the current thread into a source-tagged spec and shows a read-back before writing.

You have a target but need clarity

Use /flow-next:interview. For teams, split the interview:

/flow-next:interview fn-1 --scope=business
/flow-next:interview fn-1 --scope=technical --strategy --docs

You do not know what to build next

Use /flow-next:prospect. It ranks candidate ideas grounded in the repo, strategy, memory, and open specs.

You need product alignment

Use a business interview before the technical pass:

/flow-next:interview fn-1 --scope=business
/flow-next:interview fn-1 --scope=technical

This is the best default for teams where a PO, PM, designer, or support lead owns part of the requirement.

You need high confidence before merge

Use the full review stack:

/flow-next:plan-review fn-1
/flow-next:work fn-1
/flow-next:impl-review fn-1
/flow-next:spec-completion-review fn-1
/flow-next:make-pr fn-1

The plan review checks whether the work is safe to start. Implementation review checks the diff. Completion review checks the whole spec after all tasks are done.

You want overnight execution

Use Ralph only after specs are crisp enough to verify.

/flow-next:ralph-init
scripts/ralph/ralph_once.sh
scripts/ralph/ralph.sh

Do not use Flow-Next for

• One-line edits where no durable context matters.
• Throwaway prototypes that will not be reviewed or maintained.
• Product decisions the agent should not make.
• Work where nobody will read the spec or receipts.

When in doubt, start with a small spec. Flow-Next adds the most value when ambiguity, coordination, or review cost would otherwise dominate the work.