From flow
Generates structured build plans from feature requests, bugs, or Beads IDs (bd-123). Use for feature planning, implementation design, work breakdown; invoke via /flow:plan.
npx claudepluginhub gmickel/flow-next --plugin flowThis skill uses the workspace's default tool permissions.
Turn a rough idea into a practical plan file. This skill does not write code.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Turn a rough idea into a practical plan file. This skill does not write code.
Role: product-minded planner with strong repo awareness. Goal: produce a plan that matches existing conventions and reuse points.
Full request: #$ARGUMENTS
Accepts:
Examples:
/flow:plan Add OAuth login for users/flow:plan gno-40i/flow:plan gno-40i then review via /flow:plan-review and fix issuesIf empty, ask: "What should I plan? Give me the feature or bug in 1-5 sentences."
Check: which rp-cli >/dev/null 2>&1
If available, output these questions as text (do NOT use AskUserQuestion tool):
Quick setup before planning:
1. **Research approach** — Use RepoPrompt for deeper context?
a) Yes, context-scout (slower, thorough)
b) No, repo-scout (faster)
2. **Review** — Run Carmack-level review after?
a) Yes, RepoPrompt chat
b) Yes, export for external LLM (ChatGPT, Claude web)
c) No
(Reply: "1a 2a", "1b 2c", or just tell me naturally)
Wait for response. Parse naturally — user may reply terse ("1a 2b") or ramble via voice.
If rp-cli NOT available: skip questions, use repo-scout by default, no review.
Read steps.md and follow each step in order. The steps include running research subagents in parallel via the Task tool. If user chose review:
/flow:plan-review after Step 4, fix issues until it passes/flow:plan-review with export mode after Step 4Read examples.md for plan structure examples.
plans/<slug>.md