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.
Uses rp-cli to delegate plan/architecture reviews to RepoPrompt's context builder and chat. Triggers on "plan review", "design review", or "architecture review" mentions.
/plugin marketplace add gmickel/gmickel-claude-marketplace/plugin install flow@gmickel-claude-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
rp-cli-reference.mdworkflow.mdConduct 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.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.