Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: flow-next-plan-review description: Carmack-level plan review via rp-cli context builder + chat. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-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: <flow-epic-id> [additional context or focus areas]
Accepts:
- Flow epic ID:
fn-N
Example: /flow-next:plan-review fn-1 focus on security and error handling
Setup
FLOWCTL="${CLAUDE_PLUGIN_ROOT}/scripts/flowctl"
FIRST: Determine Review Mode
Check: which rp-cli >/dev/null 2>&1
If NOT available: inform user rp-cli is required for this skill.
Option Parsing (skip questions if found in arguments)
Parse the arguments for these patterns. If found, use them and skip the question:
Review mode:
--mode=rpor--rpor "rp chat" or "repoprompt" → RepoPrompt chat--mode=exportor--exportor "export" or "external llm" → export for external LLM
If options NOT found
If review mode was already chosen earlier in this conversation (e.g., user answered "2a" or "2b" during /flow-next:plan or /flow-next:work setup):
→ Use that mode, don't ask again.
If invoked directly without prior context, output this text (do NOT use AskUserQuestion tool):
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 user response. Parse naturally.
Get Plan Content
For Flow epic ID:
$FLOWCTL show <id> --json
$FLOWCTL cat <id>
Build a compact task table from the show output (ids, deps, statuses).
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.
More by gmickel
View allExecute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
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.
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
