spec-flow MCP — 使用場景, 安裝 & 即時演示

為什麼要用

核心特性

Five-phase workflow: Proposal → Requirements (EARS format) → Design → Tasks → Implementation
Each phase writes a Markdown doc into .spec-flow/ so decisions are auditable
Gated transitions — Claude pauses for confirmation before advancing
Multilingual triggers: English plus Chinese ('写个方案', '做个规划')
Escape hatches: --fast skips gates, --skip-design suits simpler features

即時演示

實際使用效果

spec-flow-skill.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "spec-flow-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/echoVic/spec-flow",
        "~/.claude/skills/spec-flow"
      ],
      "_inferred": true
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "spec-flow-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/echoVic/spec-flow",
        "~/.claude/skills/spec-flow"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "spec-flow-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/echoVic/spec-flow",
        "~/.claude/skills/spec-flow"
      ],
      "_inferred": true
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "spec-flow-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/echoVic/spec-flow",
        "~/.claude/skills/spec-flow"
      ],
      "_inferred": true
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "spec-flow-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/echoVic/spec-flow",
        "~/.claude/skills/spec-flow"
      ]
    }
  ]
}

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

{
  "context_servers": {
    "spec-flow-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/echoVic/spec-flow",
          "~/.claude/skills/spec-flow"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

claude mcp add spec-flow-skill -- git clone https://github.com/echoVic/spec-flow ~/.claude/skills/spec-flow

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： spec-flow

Turn a vague feature idea into a documented spec and implementation

👤 Engineers pushing back against 'just start coding' ⏱ ~60 min intermediate

何時使用： PM handed you a one-liner and you'd rather spend 20 minutes writing a spec than 2 days writing the wrong code.

前置條件

Skill cloned to ~/.claude/skills/spec-flow — git clone https://github.com/echoVic/spec-flow ~/.claude/skills/spec-flow

步驟

Invoke the workflow

spec-flow: add multi-region failover to our billing service.✓ 已複製

→ Claude writes .spec-flow/proposal.md and waits for confirmation
Confirm or edit each phase

Proposal looks good — proceed to requirements.✓ 已複製

→ requirements.md appears with EARS-format statements
Implement from the task list

Start the implementation phase. Work through tasks.md top-to-bottom.✓ 已複製

→ Code changes that map 1:1 to task checkboxes

結果： A feature ships with the spec still alive in .spec-flow/ — future you can see why every decision happened.

注意事項

You're hacking a 10-minute fix and the skill adds 4 gates — Use --fast or just skip the skill for trivial work

搭配使用： github · filesystem

Reverse-engineer a spec for existing code before refactoring

👤 Engineers inheriting undocumented modules ⏱ ~45 min intermediate

何時使用： About to refactor something nobody wrote a spec for.

步驟

Ask Spec-Flow to backfill

spec-flow --skip-design: backfill proposal and requirements.md for the existing src/auth module.✓ 已複製

→ Clean EARS requirements extracted from actual code behavior
Use the spec as refactor target

Now design phase — how would we restructure while preserving these requirements?✓ 已複製

→ design.md that maps new architecture to existing requirements

結果： A refactor grounded in a written contract instead of tribal knowledge.

搭配使用： filesystem

組合

與其他 MCP 搭配，撬動十倍槓桿

spec-flow-skill + github

Commit .spec-flow/ artifacts alongside code so the spec lives in the repo history

After implementation, commit .spec-flow/ + src/ changes in one PR titled after the proposal.✓ 已複製

spec-flow-skill + planning-with-files

Spec-Flow drives phase structure; planning-with-files keeps cross-session progress memory

Use spec-flow for the phases and planning-with-files for progress.md tracking across days.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫
proposal_phase	feature description	Start of a new feature
requirements_phase	approved proposal	After proposal confirmed
design_phase	approved requirements	After requirements confirmed; skippable with --skip-design
tasks_phase	approved design	Before implementation
implementation_phase	approved tasks	Final phase — actually build it

成本與限制

運行它的成本

API 配額: None
每次呼叫 Token 數: Each phase re-reads prior .spec-flow/ docs, so context grows across phases
費用: Free — skills are local files
提示: Use --fast on simple features; gates only earn their keep on 2+ day work.

安全

權限、密鑰、影響範圍

憑證儲存： No credentials — pure prompts

資料出站： None — .spec-flow/ stays in your working directory

.spec-flow/ files will be committed unless you .gitignore them; most teams want them committed.

故障排查

常見錯誤與修復

Skill not invoked — Claude codes without writing proposal.md

Use one of the trigger phrases exactly: 'spec-flow', 'spec mode', 'need a plan', '写个方案'.

驗證： ls ~/.claude/skills/spec-flow/SKILL.md

SKILL.md frontmatter wrong

Re-clone the repo; description is what drives auto-activation.

驗證： head ~/.claude/skills/spec-flow/SKILL.md

Wrong trigger keywords — Claude skips phases

Don't say '--fast' unintentionally. If you want full gates, omit flags and say 'spec-flow'.

替代方案

spec-flow 對比其他方案

替代方案	何時用它替代	權衡
planning-with-files	You want durable memory across sessions rather than phase gating	Different axis — complementary, not competing
Freeform dev	Feature is 1-2 hours of work	Faster, but no audit trail

spec-flow