● 社区 gmickel ⚡ 即开即用

Flow Next

Name: Flow Next (Claude Skill)
Author: gmickel

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.

▶ 观看演示 📦 安装 💡 使用场景

为什么要用

核心特性

Plan-before-execute workflow
Editable plan steps
Cross-agent (Claude Code, Codex, Factory)
Resumable mid-flow
Plans stored as Markdown

实时演示

实际使用效果

就绪

安装

作者仓库 · Claude Skills 官方文档

使用场景

实战用法： Flow Next

Plan a feature before coding

👤 Claude Code users ⏱ ~15 min intermediate

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

步骤

Trigger

Invoke flow-next with your feature description.✓ 已复制

→ Plan emitted
Edit

Tweak / reorder / drop steps.✓ 已复制

→ Approved plan
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 execution	Trivial change	Riskier on bigger work

资源

📖 阅读 GitHub 上的官方 README

🐙 查看未解决的 issue

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