Flow Next plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginTesting

Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in your repo. Claude Code · Codex · Cursor · Droid · Grok Build · OpenCode · Muse Code.

How to install Flow Next in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add gmickel/flow-next

2. Install the plugin:

grok plugin install flow-next@gmickel/flow-next --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add gmickel/flow-next, then select flow-next and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 55 skills, 30 slash commands, 1 subagent. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (25)

  • flow-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.
  • flow-next-audit — Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete / Harden per entry. Triggers on /flow-next:audit, "audit memory", "review memory", "refresh learnings", "sweep stale memory
  • flow-next-capture — Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create --plan-file` — agent-native, source-tagged, with a saved-spec summary and editor follow-up. Triggers on /flow-next:capt
  • flow-next-chart — Decision-map discovery for one oversized/unclear idea before capture. Triggers on /flow-next:chart with an unshaped idea, chart id, decision pin, --status, or stored tracker URL. Prompt-first adaptive loop - ground, chart a frontier, resolv
  • flow-next-deps — Show spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
  • flow-next-drive — Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Dete
  • flow-next-features — Seed or maintain the committed user-POV feature map at `.flow/features/` so QA and drive reuse how a user reaches each feature. Two state-resolved modes: no `.flow/features/` (or explicit init intent) seeds it; a present map maintains it. T
  • flow-next-flow — Use first in a project that uses Flow-Next for any request to implement, build, continue or deliver its specs, whatever delivery or test steps the request adds, unless the user names another skill or asks to work directly. Also for a spec o
  • flow-next-impl-review — John Carmack-level implementation review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
  • flow-next-land — Resolve feedback and CI for one named pull request, then squash merge when currently authorized and ready. Emits LAND_VERDICT. Use when asked to land a pull request.
  • flow-next-make-pr — Render a briefing from the aid artifact and open or update a PR via gh. Auto-detects the spec from the branch. Supports --draft, --ready, --base, --memory, --dry-run, --update, and mode:autonomous.
  • flow-next-map — Wrap `clawpatch map` to produce a semantic feature index of the repo (~20 languages, persisted at `.clawpatch/features/*.json`). Detects install, runs `clawpatch init` when `.clawpatch/` absent, invokes provider-free `clawpatch map --source
  • flow-next-memory-migrate — Migrate legacy flat memory files (`.flow/memory/pitfalls.md`, `conventions.md`, `decisions.md`) into the categorized YAML schema. Triggers on /flow-next:memory-migrate, "migrate memory", "convert legacy memory", "lift pitfalls into categori
  • flow-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.
  • flow-next-plan-review — Carmack-level plan review via Codex, Copilot, Cursor, Claude or a host reviewer. Use when reviewing Flow specs or design docs. Triggers on /flow-next:plan-review.
  • flow-next-prime — Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked n
  • flow-next-prose — Use while drafting any substantial reply, report, review walkthrough, or summary for the user - read the artifact prose contract before writing, not after, and draft under its rules. Do not use for short conversational turns, tool-call narr
  • flow-next-prospect — Generate ranked candidate ideas grounded in the repo, upstream of /flow-next:plan. Triggers on /flow-next:prospect with an optional focus hint (concept, path, constraint, or volume).
  • flow-next-qa — Live-app real-user QA pass derived from the spec. Drives the running app via flow-next-drive, derives scenarios from the spec's AC / R-IDs / boundaries, files structured P0/P1/P2 findings with evidence, and ends with a YES/NO ship verdict r
  • flow-next-refine — Refine a spec, task, or spec file before building - one question pass for the decisions that would change what gets built, optionally focused by a free-text --scope lens (business, technical, qa, ...), or a read-only research pass (--scope=
  • flow-next-resolve-pr — Resolve PR review feedback — fetch unresolved threads, triage, dispatch per-thread resolver agents, validate, commit, reply + resolve via GraphQL. Triggers on /flow-next:resolve-pr.
  • flow-next-setup — Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions, plus a commented model-routing example proposed into the project instruction file. Use when user runs /flow-next:setup.
  • flow-next-spec-completion-review — Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
  • flow-next-strategy — Create or maintain `STRATEGY.md` — the product's target problem, our approach, who it's for, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadma
  • flow-next-sync — Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.

Subagents (15)

  • flow-next:build-scout — Used by /flow-next:prime to analyze build system, scripts, and CI configuration. Do not invoke directly.
  • flow-next:claude-md-scout — Used by /flow-next:prime to analyze CLAUDE.md and AGENTS.md quality and completeness. Do not invoke directly.
  • flow-next:docs-gap-scout — Identify documentation that may need updates based on the planned changes.
  • flow-next:docs-scout — Find the most relevant framework/library docs for the requested change.
  • flow-next:env-scout — Used by /flow-next:prime to scan for environment setup, .env templates, Docker, and devcontainer configuration. Do not invoke directly.
  • flow-next:flow-gap-analyst — Map user flows, edge cases, and missing requirements from a brief spec.
  • flow-next:github-scout — Search GitHub repos (public + private) for code patterns, implementations, and examples.
  • flow-next:memory-scout — Search .flow/memory/ for entries relevant to the current task or request.
  • flow-next:observability-scout — Used by /flow-next:prime to scan for observability setup including logging, tracing, metrics, and health endpoints. Do not invoke directly.
  • flow-next:plan-sync — Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
  • flow-next:pr-comment-resolver — Resolve a single PR review thread by evaluating validity, implementing fixes, or replying. Spawned by flow-next-resolve-pr skill; not for direct user invocation.
  • flow-next:practice-scout — Gather modern best practices and pitfalls for the requested change.
  • flow-next:quality-auditor — Single-axis quality audit of recent changes — correctness or standards, per the AXIS line in the dispatch.
  • flow-next:repo-scout — Scan repo to find existing patterns, conventions, and related code paths for a requested change.
  • flow-next:security-scout — Used by /flow-next:prime to scan for security configuration including GitHub settings, CODEOWNERS, and dependency updates. Do not invoke directly.

About this listing

Flow Next is a community plugin on GitHub by gmickel, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 25 skills, 15 subagents. Its license is MIT. We checked commit 27c446cbe4ed. It's one of 34 listings in the Testing category on GrokStacks.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

Flow Next FAQ

How do I install Flow Next in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add gmickel/flow-next, then run grok plugin install flow-next@gmickel/flow-next --trust. Then start a new Grok session, or press r in /plugins, to load it.

Is Flow Next an official Grok Build plugin?

No. Flow Next is a community plugin on GitHub by gmickel, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does Flow Next include?

According to what Grok loaded in our install check, Flow Next includes 25 skills, 15 subagents: flow-next, flow-next-audit, flow-next-capture, flow-next-chart, flow-next-deps, flow-next-drive….

Details

Type
Plugin
Category
Testing
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
gmickel
Keywords
agentic-workflow, ai-agent, ai-workflow, anthropic, autonomous-agent, claude-code, claude-code-plugin, cli, code-review, codex, execution, factory-droid
Source repo
https://github.com/gmickel/flow-next
Checked commit
27c446cbe4ed
Homepage
https://flow-next.dev
Checked by GrokStacks
Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain Flow Next? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/flow-next/)

HTML

<a href="https://grokstacks.com/p/flow-next/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

<a href="https://grokstacks.com/p/flow-next/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Flow Next</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 25 skills, 15 subagents</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Flow Next on GrokStacks](https://grokstacks.com/p/flow-next/)**: Community plugin for Grok Build with 25 skills, 15 subagents. Install: `grok plugin install flow-next@gmickel/flow-next --trust` (after `grok plugin marketplace add gmickel/flow-next`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Testing

Agentic Qe

Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support testing activities for a product at any stage of the SDLC. Free to use, fork, build, and contribute. Based on the Agentic QE Framework created by Dragan Spiridonov.

Community Claude Code plugin, installs in GrokPluginTestingMCP: manual setup

Brooks Lint

AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix

Community Claude Code plugin, installs in GrokPluginTesting

Cavekit

Frozen — compressed spec-driven development plugin for Claude Code. Still works; active development moved to JuliusBrussee/caveman.

Community Claude Code plugin, installs in GrokPluginTesting

Cc 1c Skills

Набор навыков для AI(ИИ)-агентов (Claude Code, Cursor, Codex и др.), помогающий охватить полный цикл разработки на платформе 1С:Предприятие 8.3. Даёт модели абстракции над XML-форматами и CLI конфигуратора, а также глаза и руки для тестирования через веб-клиент. AI skills for 1C:Enterprise 8.3.

Community Claude Code plugin, installs in GrokPluginTesting

Claude Night Market

23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.

Community Claude Code plugin, installs in GrokPluginTesting

Claude Skills Marketplace

Claude Code Skills for software engineering workflows - Git automation, testing, and code review

Community Claude Code plugin, installs in GrokPluginTesting

All 34 testing listings →