gmickel/flow-plan-review
plugins/flow/skills/flow-plan-review/SKILL.md
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
$ install --global
skillsauthnpx skillsauth add gmickel/gmickel-claude-marketplace flow-plan-reviewInstall 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.3s3 files scanned
SKILL.md
- name:
- flow-plan-review
- description:
- Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
Plan Review Mode (CLI)
Conduct a John Carmack-level review of implementation plans using RepoPrompt's context builder and chat.
Role: Code Review Coordinator (NOT the reviewer) Tool: rp-cli for context building and chat delegation
Input
Arguments: #$ARGUMENTS
Format: <plan-file-or-beads-id> [additional context or focus areas]
Accepts:
- Plan file path:
plans/<slug>.md - Beads ID(s) or title(s) directly
Example: /flow:plan-review docs/plan/auth-refactor.md focus on security and error handling
FIRST: Determine Review Mode
Check: which rp-cli >/dev/null 2>&1
If NOT available: inform user rp-cli is required for this skill.
If review mode was already chosen earlier in this conversation (e.g., user answered "2a" or "2b" during /flow:plan or /flow:work setup):
→ Use that mode, don't ask again.
If invoked directly without prior context, ask:
Both modes use RepoPrompt for context building (builder, file selection, codemaps).
The difference is where the review happens:
Review mode:
a) RepoPrompt chat (default) — review via rp-cli chat
b) Export for external LLM — export context file for ChatGPT, Claude web, etc.
(Reply: "a", "b", "export", or just tell me)
Wait for response. Parse naturally.
Critical Requirement
DO NOT REVIEW THE PLAN YOURSELF – you are a coordinator, not the reviewer.
Your job is to:
- Use
rp-cli -e 'windows'to find the RepoPrompt window - Use
rp-cli -w <id> -e 'builder ...'to build context around the plan - Use
rp-cli -w <id> -e 'chat ...'to execute the review
The RepoPrompt chat conducts the actual review with full file context.
Workflow
Read workflow.md and follow each phase in order. Phases include window selection, context building, and review execution.
rp-cli Reference
Read rp-cli-reference.md for command syntax and examples.
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