flow-next

Epic completion review - verify implementation matches spec

John Carmack-level implementation review via RepoPrompt or Codex

Interview & refine an epic, task, or spec file in-depth

Carmack-level plan review via RepoPrompt or Codex

Draft a structured build plan from a short request

Used by /flow-next:prime to analyze build system, scripts, and CI configuration. Do not invoke directly.

Used by /flow-next:prime to analyze CLAUDE.md and AGENTS.md quality and completeness. Do not invoke directly.

Token-efficient codebase exploration using RepoPrompt codemaps and slices. Use when you need deep codebase understanding without bloating context.

Identify documentation that may need updates based on the planned changes.

Find the most relevant framework/library docs for the requested change.

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".

Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path', 'which epics can run in parallel'.

Epic completion review - verifies all epic tasks implement spec requirements. Triggers on /flow-next:epic-review.

Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.

John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.

5 hooks across 4 events