gmickel/flow-next

Codebase Feature Map wraps a feature-mapping CLI to generate and read semantic repo maps. Use it to enrich scout context, inspect detected features, and surface a map as a discoverability aid when one exists.

Export Context builds RepoPrompt review context and saves it as a markdown file for external LLM review. Use it when you want to share plan or implementation context with ChatGPT, Claude web, or another model.

Flow Interview conducts a deep interview about a spec, task, or spec file to capture implementation details before work begins. Use it to refine requirements, clarify scope, and write the results back through Flow task tracking.

Flow Interview conducts a thorough interview about a task, spec, or spec file to capture unresolved implementation details. Use it before building when requirements need refinement or clarification.

Flow Next Audit reviews `.flow/memory/` entries against the current codebase and decides whether to keep, update, consolidate, replace, or delete each one. Use it to refresh stale memory and resolve overlapping entries.

Flow Next Audit reviews `.flow/memory/` entries against the current codebase and decides whether to keep, update, consolidate, replace, delete, or harden each one. Use it when memory entries may be stale, overlapping, or ready to become a gate.

Flow Next Capture turns a conversation into a flow-next spec with source tags, then asks for read-back before writing it. Use it when a discussion has enough detail to become `.flow/specs/<spec-id>.md`.

Flow Next Capture turns recent conversation context into a flow-next spec file under `.flow/specs/` using `flowctl spec create` and `spec set-plan`. It is used when a discussion needs to be locked into a source-tagged spec before the context is lost.

Flow Next Chart finds the next decision to resolve for one oversized idea before capture. Use it to ground an unclear request, map the frontier, and hand back a briefing for /flow-next:capture.

Flow Next Deps shows spec dependency graphs, blocking chains, and execution phases. Use it to see what is blocked, what can run in parallel, and the critical path for spec execution.

Flow Next Drive routes UI automation to the best available driver for web, Chromium-backed desktop, or native apps. Use it to navigate, verify UI, capture screenshots, fill forms, or run sign-in and e2e flows.

Flow Next Guide recommends the smallest sufficient flow-next route for a situation. Use it when you need to choose between strategy, prospecting, charting, capture, interview, plan, work, or visual review.

Flow Next Implementation Review coordinates backend-specific code reviews for implementation changes, PRs, or branches. Use it when you want a structured review via Codex, Copilot, Cursor, host, or RepoPrompt.

Flow Next Land advances open PRs authored by the build loop through CI checks, review handling, and merge gates on each cadence tick. Use it when you want an autonomous driver to keep PRs moving and report a terminal verdict.

Flow Next Make PR renders a structured pull request body from flow-next state and opens it with gh. Use it when you want a draft or ready PR created from the current spec, diff, and evidence without manual assembly.

Flow Next Make Pr renders a reviewable PR body from flow-next state and creates the pull request with gh. It is used when you want a structured draft or ready PR from a spec, diff, and collected project context.

Flow Next Map wraps `clawpatch map` to build a semantic feature index in `.clawpatch/features/*.json`. Use it to initialize clawpatch, run the map step, and pass through extra map arguments when needed.

Flow Next Memory Migrate converts legacy flat memory files into the categorized YAML schema used by flow-next. Use it when upgrading pre-fn-30 memory files or migrating old pitfalls, conventions, and decisions entries.

Flow Next Pilot advances one ready spec by exactly one pipeline stage per invocation and ends with a PILOT_VERDICT for the driver. Use it to run plan, review, work, qa, or make-pr steps in a host-controlled loop without asking the user questions.

Flow Next Plan creates structured specs and task lists from feature requests or Flow IDs. Use it when planning a feature or refining an implementation plan without writing code.

Flow Next Plan creates structured build plans from feature requests or Flow IDs. Use it when turning an understood request into a spec and task breakdown in .flow/ before implementation.

Flow Next Plan Review reviews Flow specs and design docs through RepoPrompt, Codex, or other supported backends. Use it when running /flow-next:plan-review to evaluate plans and route fixes.

Flow Next Prospect generates and critiques candidate ideas from the repo, then writes a ranked prospect artifact for handoff to interview or plan. Use it when deciding what to pursue next from a focus hint, path, or constraint.

Human-First Visual Digest restates specs, tasks, diffs, or conversation topics as compact markdown visuals. Use it when a review needs a quick structural view instead of long prose.

Synthetic Probe reads one of two reference files based on the selected route and returns the token it finds. Use it in eval arenas where an agent must follow a constrained file-reading path.