gmickel/flow-plan
plugins/flow/skills/flow-plan/SKILL.md
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
$ install --global
skillsauthnpx skillsauth add gmickel/gmickel-claude-marketplace flow-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 1:25 PM4.4s3 files scanned
SKILL.md
- name:
- flow-plan
- description:
- Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
Flow 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
Related Skills
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
630SKILL.mdUpdated May 8, 2026
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
630SKILL.mdUpdated May 8, 2026
gmickel/flow-next-capture
testing
VerifiedTrustedCommunity
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the compaction-detection refusal; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision).
630SKILL.mdUpdated Apr 26, 2026
gmickel/flow-next-capture
testing
VerifiedTrustedCommunity
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the compaction-detection refusal; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision).
630SKILL.mdUpdated Apr 26, 2026