flow-next — Claude Code and Codex plugin: what it does, how to install
flow-next runs a change from spec to pull request: specs stay in the repo, plans fit the context window, and a second model handles the review.
MIT ★ 730 updated 2026-10-29
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-nextWhat flow-next does
flow-next drives a change from a written spec that sits in the repo and survives between sessions. The plan gets cut to fit the context window, and workers are re-anchored mid-task once that window runs tight.
A second model reviews the diff, which catches what the author stopped seeing. Inside: 21 subagents, 26 slash commands and 29 skills. Config and run artifacts collect under .flow/, and the flowctl CLI has a reference page of its own. Nothing external needs installing.
Autonomous runs go through flow --auto, and the plugin is listed for Claude and Codex. One catch: Ralph was dropped in 7.0, so pipelines that still call it need the 6.7.x line pinned.
What it helps with
- take a change from spec to a landed pull request
- fit a work plan into the context window
- get a second model to review the diff
- keep specs and run artifacts next to the code in
.flow/ - run the loop autonomously with
flow --auto
Example prompts for the agent
- Turn this task into a spec under
.flow/and show me the plan before any code changes. - Run
flow --autoand halt if a worker drifts off the plan. - Send the diff through a cross-model review and list what comes back.
How to install flow-next
Plugin marketplace
/plugin marketplace add gmickel/flow-next/plugin install flow-next@flow-nextStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about flow-next
How do I install flow-next in Claude Code?
Run /plugin marketplace add gmickel/flow-next first, then /plugin install flow-next@flow-next.
What does flow-next do?
It runs an agent through a spec-driven loop: a plan sized to the context window, workers re-anchored on the task, and a review from a second model. Specs and artifacts stay in .flow/ inside the repo.
Does flow-next still include Ralph?
No. Ralph was removed in 7.0; pin 6.7.x if your pipeline still depends on it.
Source text
flow-next · MIT
# flow-next > **Repeatable agentic engineering.** Durable specs, re-anchored workers, adversarial reviews, receipts — everything in your repo, zero external dependencies. ### 🌐 [Full Documentation Site → flow-next.dev](https://flow-next.dev) This is the plugin source directory. The canonical README for flow-next lives at the [repository root](../../README.md). - Install and your first change → [root README](../../README.md#install) - What it does and how fast → [root README](../../README.md#how-much-faster-and-how-much-better) - Skills catalog (all 29 skills) → [`docs/skills.md`](docs/skills.md) - Adopting in a team → [`docs/teams.md`](docs/teams.md) - `flowctl` CLI reference → [`docs/flowctl.md`](docs/flowctl.md) - Going autonomous (`flow --auto` / land) → [root README → Land a pull request](../../README.md#land-a-pull-request). Ralph was removed in 7.0; pin 6.7.x if you still need it. - Architecture + `.flow/` layout → [`docs/architecture.md`](docs/architecture.md) - Full doc index → [`docs/README.md`](docs/README.md)
© Gordon Mickel · MIT · gmickel/flow-next