From flow
Coordinates Carmack-level reviews of implementation plans, architecture docs, and design specs using rp-cli for repo context building and RepoPrompt chat delegation.
npx claudepluginhub gmickel/flow-next --plugin flowThis skill uses the workspace's default tool permissions.
Conduct a John Carmack-level review of implementation plans using RepoPrompt's context builder and chat.
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.
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
Arguments: #$ARGUMENTS
Format: <plan-file-or-beads-id> [additional context or focus areas]
Accepts:
plans/<slug>.mdExample: /flow:plan-review docs/plan/auth-refactor.md focus on security and error handling
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.
DO NOT REVIEW THE PLAN YOURSELF – you are a coordinator, not the reviewer.
Your job is to:
rp-cli -e 'windows' to find the RepoPrompt windowrp-cli -w <id> -e 'builder ...' to build context around the planrp-cli -w <id> -e 'chat ...' to execute the reviewThe RepoPrompt chat conducts the actual review with full file context.
Read workflow.md and follow each phase in order. Phases include window selection, context building, and review execution.
Read rp-cli-reference.md for command syntax and examples.