How do I install the Flow Plan Review skill?

Run npx skillmds@latest add tomevault-io/flow-plan-review-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flow Plan Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flow Plan Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flow Plan Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flow Plan Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flow Plan Review by tomevault-io — Agent Skill

Name: Flow Plan Review
Author: tomevault-io

Flow Plan Review

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. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

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.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: flow-plan-review-2description: 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. Use when this capability is needed.---# 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## InputArguments: #$ARGUMENTSFormat: `<plan-file-or-beads-id> [additional context or focus areas]`Accepts:- Plan file path: `plans/<slug>.md`- Beads ID(s) or title(s) directlyExample: `/flow:plan-review docs/plan/auth-refactor.md focus on security and error handling`## FIRST: Determine Review ModeCheck: `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 chatb) 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:1. Use `rp-cli -e 'windows'` to find the RepoPrompt window2. Use `rp-cli -w <id> -e 'builder ...'` to build context around the plan3. Use `rp-cli -w <id> -e 'chat ...'` to execute the reviewThe **RepoPrompt chat** conducts the actual review with full file context.## WorkflowRead [workflow.md](workflow.md) and follow each phase in order. Phases include window selection, context building, and review execution.## rp-cli ReferenceRead [rp-cli-reference.md](rp-cli-reference.md) for command syntax and examples.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/gmickel) — claim your Tome and manage your conversions.

Frequently asked questions