From flow-next
Drafts a structured build plan from a short idea or fn-N request, with optional --research (rp|grep) and --review (rp|export|none) flags.
How this command is triggered — by the user, by Claude, or both
Slash command
/flow-next:plan <idea or fn-N> [--research=rp|grep] [--review=rp|export|none]flow-next/The summary Claude sees in its command listing — used to decide when to auto-load this command
# IMPORTANT: This command MUST invoke the skill `flow-next-plan` The ONLY purpose of this command is to call the `flow-next-plan` skill. You MUST use that skill now. **User request:** $ARGUMENTS Pass the user request to the skill. The skill handles all planning logic.
flow-next-planThe ONLY purpose of this command is to call the flow-next-plan skill. You MUST use that skill now.
User request: $ARGUMENTS
Pass the user request to the skill. The skill handles all planning logic.
npx claudepluginhub tiendung/flow-next2plugins reuse this command
First indexed Jan 9, 2026
/planDrafts a structured build plan from a short idea or fn-N request, with optional --research (rp|grep) and --review (rp|export|none) flags.
/planCreates a detailed plan for a project phase through research, planning, and verification before building.
/create-planCreates detailed implementation plans through interactive research and iteration for tasks or files, with configurable autonomy: autopilot, critical, verbose.
/planCreates detailed implementation plans interactively through research docs, file reads, and user dialog for features, refactors, or integrations.
/planTurns a feature request or research document into a phased, build-ready implementation plan with explicit interfaces, gates, and skills per phase.
/planCreates actionable phase/task structures from planning input like files or descriptions, generating .claudio/phase*/ directories with tasks.md files and claude.md contexts for execution.