● 社群 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