by gmickel · gmickel/flow-next
Plan-first orchestration: every non-trivial ask becomes a checkable plan you can edit before any code is written.
Flow Next slots between you and the agent: it prompts for a structured plan first, you approve, then execution. Works across Claude Code, OpenAI Codex, and Factory Droid.
%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"flow-next-skill": {
"command": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
],
"_inferred": true
}
}
}Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.
{
"mcpServers": {
"flow-next-skill": {
"command": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
],
"_inferred": true
}
}
}Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.
{
"mcpServers": {
"flow-next-skill": {
"command": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
],
"_inferred": true
}
}
}Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".
{
"mcpServers": {
"flow-next-skill": {
"command": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
],
"_inferred": true
}
}
}Same shape as Claude Desktop. Restart Windsurf to pick up changes.
{
"mcpServers": [
{
"name": "flow-next-skill",
"command": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
]
}
]
}Continue uses an array of server objects rather than a map.
{
"context_servers": {
"flow-next-skill": {
"command": {
"path": "git",
"args": [
"clone",
"https://github.com/gmickel/flow-next"
]
}
}
}
}Add to context_servers. Zed hot-reloads on save.
claude mcp add flow-next-skill -- git clone https://github.com/gmickel/flow-nextOne-liner. Verify with claude mcp list. Remove with claude mcp remove.
When to use: You want to align on approach before agents start writing.
Outcome: Reviewed plan executed without surprise scope creep.
Attach the plan to the PR for reviewer context
| Tool | Inputs | When to call | Cost |
|---|---|---|---|
| plan / approve / execute | (see docs) | Three-phase command surface | 1 call |
fs-read fs-writePlan too vagueAsk for "concrete file paths" in the brief
| Alternative | When to use it instead | Tradeoff |
|---|---|---|
| Direct execution | Trivial change | Riskier on bigger work |