flow-plan
npx machina-cli add skill gmickel/gmickel-claude-marketplace/flow-plan --openclawFlow plan
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.
Input
Full request: #$ARGUMENTS
Accepts:
- Feature/bug description in natural language
- Beads ID(s) or title(s) to plan for
- Chained instructions like "then review with /flow:plan-review"
Examples:
/flow:plan Add OAuth login for users/flow:plan gno-40i/flow:plan gno-40i then review via /flow:plan-review and fix issues
If empty, ask: "What should I plan? Give me the feature or bug in 1-5 sentences."
FIRST: Setup Questions (if rp-cli available)
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.
Workflow
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:
- Option 2a: run
/flow:plan-reviewafter Step 4, fix issues until it passes - Option 2b: run
/flow:plan-reviewwith export mode after Step 4
Examples
Read examples.md for plan structure examples.
Output
- Standard:
plans/<slug>.md - Beads: epic/tasks/subtasks in Beads (no file written)
Output rules
- Only write the plan file (or create Beads epic)
- No code changes
Source
git clone https://github.com/gmickel/gmickel-claude-marketplace/blob/main/plugins/flow/skills/flow-plan/SKILL.mdView on GitHub Overview
Flow-plan converts rough feature requests, bug reports, or Beads IDs into practical plan files that follow existing conventions and reuse points. It helps product-minded planning by outlining scope, tasks, and milestones without writing code. The output targets plan files or Beads epics to support seamless handoffs.
How This Skill Works
Trigger with /flow:plan followed by a natural language description or Beads IDs. The skill acts as a product-minded planner with repo awareness, reads the full request, and follows the documented workflow to generate a plans/<slug>.md file or Beads epic. It can chain actions (e.g., then review via /flow:plan-review) and prompts for missing details when needed.
When to Use It
- When turning a user story or bug report into a concrete plan before implementation
- When designing implementation details and a work breakdown structure
- When given Beads ID(s) or titles to plan around
- When you need to ensure the plan aligns with repository conventions and reuse points
- When you want to review and refine the plan with a subsequent /flow:plan-review step
Quick Start
- Step 1: Trigger with /flow:plan and provide a feature/bug description or Beads ID
- Step 2: If needed, include multiple beads or chained steps (e.g., gno-40i then /flow:plan-review)
- Step 3: Receive a plans/<slug>.md file (or Beads epic) ready for review
Best Practices
- Start with a clear, single-sentence description of the request
- Leverage Beads IDs or titles to pull contextual information
- Follow existing conventions and identify reuse points across the repo
- Break work into milestones, epics, tasks, and subtasks
- Use the optional plan-review flow to validate and adjust the plan
Example Use Cases
- /flow:plan Add OAuth login for users
- /flow:plan gno-40i
- /flow:plan gno-40i then review via /flow:plan-review and fix issues
- /flow:plan Refactor dashboard widgets for improved responsiveness
- /flow:plan bd-123 Fix crash on startup and ensure crashlytics logs
