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

Analyze codebase for agent readiness and propose improvements

Scaffold repo-local Ralph autonomous harness (scripts/ralph/)

Optional local install of flowctl CLI and project docs

Manually trigger plan-sync to update downstream task specs after implementation drift

Remove flow-next files from project

Execute a plan end-to-end with checks

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.

Used by /flow-next:prime to scan for environment setup, .env templates, Docker, and devcontainer configuration. Do not invoke directly.

Scan existing epics to find dependencies and relationships for a new plan.

Map user flows, edge cases, and missing requirements from a brief spec.

Search GitHub repos (public + private) for code patterns, implementations, and examples.

Search .flow/memory/ for entries relevant to the current task or request.

Used by /flow-next:prime to scan for observability setup including logging, tracing, metrics, and health endpoints. Do not invoke directly.

Synchronizes downstream task specs after implementation. Spawned by flow-next-work after each task completes. Do not invoke directly.

Gather modern best practices and pitfalls for the requested change.

Review recent changes for correctness, simplicity, security, and test coverage.

Scan repo to find existing patterns, conventions, and related code paths for a requested change.

Used by /flow-next:prime to scan for security configuration including GitHub settings, CODEOWNERS, and dependency updates. Do not invoke directly.

Used by /flow-next:prime to analyze test framework setup, coverage configuration, and test commands. Do not invoke directly.

Used by /flow-next:prime to scan for linting, formatting, type checking, and pre-commit configuration. Do not invoke directly.

Task implementation worker. Spawned by flow-next-work to implement a single task with fresh context. Do not invoke directly - use /flow-next:work instead.

Used by /flow-next:prime to scan for CI/CD, PR templates, issue templates, and workflow automation. Do not invoke directly.

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.

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.

Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.

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

Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.

Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.

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.

Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.

Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.

Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work 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).

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.

Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', '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.

5 hooks across 4 events