flow-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: <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
More from gmickel/gmickel-claude-marketplace
flow-next-plan-review
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
22flow-next
Manage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.
21flow-next-interview
Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
20flow-next-plan
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
20flow-next-ralph-init
Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
20browser
Browser automation via agent-browser CLI. Use when you need to navigate websites, verify deployed UI, test web apps, read online documentation, scrape data, fill forms, capture baseline screenshots before design work, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign".
19