Gmickel Flow Next
gmickel-flow-next is a Claude Code plugin for the Build phase that enforces plan-first task tracking, worker subagents, optional Ralph autonomous mode, and cross-model reviews across multiple coding agents.
by gmickel · github.com/gmickel/flow-next
Install when you want a plan-first, gate-driven agent workflow with tracking and optional autonomous Ralph runs across Claude Code, Codex, and Factory Droid.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install gmickel-flow-next@gmickel/flow-nextBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:gmickel/flow-next") and the paste-ready config with skillselion.get_install_config("plugin:gmickel/flow-next").
What it does
gmickel-flow-next is a Claude Code plugin bundle for solo builders who are tired of agents jumping straight into edits without a shared plan. It enforces a plan-first pipeline: scope work, track tasks without extra infrastructure, delegate to worker subagents with context isolation, and optionally let Ralph run in autonomous mode for longer jobs. Cross-model review hooks help you sanity-check output when you mix Claude Code with Codex or Factory Droid. The catalog lists two related plugins in one repo, aimed at agent-tooling and PM-style orchestration rather than a single API integration. Use it when your bottleneck is coordination—gates, commands, and review—not when you only need a one-off skill. It pairs naturally with writing-plans-style habits but ships as installable plugin commands and skills for day-to-day coding agents.
Highlights
- Plan-first workflow with execution gates before subagents write code
- Zero-dependency task tracking (beads) and worker subagent isolation
- Ralph autonomous mode for extended agent loops
- Cross-model reviews across Claude Code, OpenAI Codex, and Factory Droid
- Bundle of 2 plugins with optional two-step and multimodel flows
Why builders use it
Agents often execute before you have a tracked plan, so parallel subagents collide, context bleeds, and nobody reviews output before merge.
You get gated, trackable work units, isolated workers, and optional autonomous or cross-model review passes before code lands on main.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 562 stars, 0 votes.
FAQ
Who is gmickel-flow-next for?
Solo and small-team builders using Claude Code, Codex, or Factory Droid who want plan-first gates, task tracking, and subagent workers without standing up extra PM tooling.
When should I use gmickel-flow-next?
Use it at the start of a non-trivial build or refactor when you need beads-style tracking, execution gates, Ralph autonomous runs, or reviews across more than one model.
How do I add gmickel-flow-next to my agent?
Install the gmickel/flow-next plugin bundle from the Claude Code plugin marketplace or repo, enable both bundled plugins, then invoke Flow commands and skills from your session before delegating work to subagents.
Comments
Share how you use gmickel-flow-next, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.