/ 目录 / 演练场 / Flow Next
● 社区 gmickel ⚡ 即开即用

Flow Next

作者 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.

为什么要用

核心特性

实时演示

实际使用效果

就绪

安装

选择你的客户端

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "flow-next-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gmickel/flow-next"
      ],
      "_inferred": true
    }
  }
}

打开 Claude Desktop → Settings → Developer → Edit Config。保存后重启应用。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "flow-next-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gmickel/flow-next"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用与 Claude Desktop 相同的 mcpServers 格式。项目级配置优先于全局。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "flow-next-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gmickel/flow-next"
      ],
      "_inferred": true
    }
  }
}

点击 Cline 侧栏中的 MCP Servers 图标,然后选 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "flow-next-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gmickel/flow-next"
      ],
      "_inferred": true
    }
  }
}

格式与 Claude Desktop 相同。重启 Windsurf 生效。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "flow-next-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gmickel/flow-next"
      ]
    }
  ]
}

Continue 使用服务器对象数组,而非映射。

~/.config/zed/settings.json
{
  "context_servers": {
    "flow-next-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/gmickel/flow-next"
        ]
      }
    }
  }
}

加入 context_servers。Zed 保存后热重载。

claude mcp add flow-next-skill -- git clone https://github.com/gmickel/flow-next

一行命令搞定。用 claude mcp list 验证,claude mcp remove 卸载。

使用场景

实战用法: Flow Next

Plan a feature before coding

👤 Claude Code users ⏱ ~15 min intermediate

何时使用: You want to align on approach before agents start writing.

步骤
  1. Trigger
    Invoke flow-next with your feature description.✓ 已复制
    → Plan emitted
  2. Edit
    Tweak / reorder / drop steps.✓ 已复制
    → Approved plan
  3. Execute
    Run the plan; agent ticks steps as they complete.✓ 已复制
    → Feature built per plan

结果: Reviewed plan executed without surprise scope creep.

组合

与其他 MCP 搭配,撬动十倍杠杆

flow-next-skill + github

Attach the plan to the PR for reviewer context

Combine flow-next-skill with github: Attach the plan to the PR for reviewer context✓ 已复制

工具

此 MCP 暴露的能力

工具输入参数何时调用成本
plan / approve / execute (see docs) Three-phase command surface 1 call

成本与限制

运行它的成本

API 配额
N/A
每次调用 Token 数
Plans add ~1 plan-sized round-trip
费用
Free
提示
Save plans alongside the PR — great for retros

安全

权限、密钥、影响范围

最小权限: fs-read fs-write
凭据存储: None
数据出站: None

故障排查

常见错误与修复

Plan too vague

Ask for "concrete file paths" in the brief

替代方案

Flow Next 对比其他方案

替代方案何时用它替代权衡
Direct executionTrivial changeRiskier on bigger work

更多

资源

📖 阅读 GitHub 上的官方 README

🐙 查看未解决的 issue

🔍 浏览全部 400+ MCP 服务器和 Skills