strategic-partner MCP — 使用場景, 安裝 & 即時演示

為什麼要用

核心特性

Premise challenge against 4 trigger conditions before any work starts
Forced 'Path A/B/C' alternatives with tradeoffs — no single-option proposals
Confidence labels: [SAFE] vs [RISK] on recommendations
Advisory Completion Gate — 5 conditions must hold before executor prompt is crafted
14 named cognitive heuristics applied to specific decision types

即時演示

實際使用效果

strategic-partner-skill.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

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

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

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

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

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

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

VS Code → Cline → MCP Servers → Edit

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

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "strategic-partner-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JimmySadek/strategic-partner",
        "~/.claude/skills/strategic-partner"
      ]
    }
  ]
}

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

~/.config/zed/settings.json

{
  "context_servers": {
    "strategic-partner-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/JimmySadek/strategic-partner",
          "~/.claude/skills/strategic-partner"
        ]
      }
    }
  }
}

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

claude mcp add strategic-partner-skill -- git clone https://github.com/JimmySadek/strategic-partner ~/.claude/skills/strategic-partner

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

使用場景

實戰用法： strategic-partner

Run a decision through the advisor before touching code

👤 Tech leads and founders who suspect they'd regret building too soon ⏱ ~30 min intermediate

何時使用： You're about to ask Claude Code to build something substantial. Pause and consult the advisor first.

前置條件

Skill cloned — git clone https://github.com/JimmySadek/strategic-partner ~/.claude/skills/strategic-partner

步驟

Open the advisory session

Using strategic-partner — I'm about to add a queue system to handle email sends. Challenge my premise first.✓ 已複製

→ Claude probes whether a queue is actually needed vs simpler alternatives
Receive Path A/B/C

Give me three paths with tradeoffs.✓ 已複製

→ Three distinct paths, each labeled [SAFE] or [RISK], with honest downsides
Cross Completion Gate

I pick Path B. Prepare the executor prompt.✓ 已複製

→ Gate check runs; if conditions aren't met, you're pushed back to advisory
Hand off to executor

Open a fresh Claude Code session and paste the executor prompt.✓ 已複製

→ Execution session works with clean context

結果： Work that's been decided deliberately rather than drifted into.

注意事項

Using the advisor as a rubber stamp — If you're always picking 'Path A — do what I said', the premise challenge isn't working — provide real context

搭配使用： github

Run a weekly strategy review with the persistent advisor

👤 Solo operators without a real chief-of-staff ⏱ ~30 min beginner

何時使用： Friday afternoon, closing out the week.

步驟

Review decisions made this week

strategic-partner — review this week's advisory log. Which decisions do I now have evidence to revise?✓ 已複製

→ Specific call-outs of decisions where execution revealed something new
Plan next week

What's the one decision next week that most deserves premise challenge?✓ 已複製

→ Pinpoint rather than a to-do list

結果： A weekly audit that compounds across months.

搭配使用： planning-with-files

組合

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

strategic-partner-skill + planning-with-files

Persist the advisor's decision log across sessions in findings.md / progress.md

Use planning-with-files — keep decisions.md updated every advisory session.✓ 已複製

strategic-partner-skill + github

When executor session commits, reference the decision from advisor log in the PR body

After executor finishes, link the advisor decision ID in the PR description.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫
premise_challenge	intended work + context	Before any substantial build
forced_alternatives	problem statement	Once premise passes; before committing to one path
completion_gate	chosen path + context	Before crafting executor prompt
executor_prompt_craft	decision + context	Handoff to execution
decision_log	current session state	Throughout advisory session

成本與限制

運行它的成本

API 配額: None
每次呼叫 Token 數: Advisor sessions carry persistent context — can grow
費用: Free — skills are local files
提示: Trim the decision log periodically; stale decisions bloat context.

安全

權限、密鑰、影響範圍

憑證儲存： No credentials — pure prompts

資料出站： None

This skill deliberately slows you down on important decisions. That's the feature — don't work around it.

故障排查

常見錯誤與修復

Skill not invoked — Claude jumps to building

Say 'use strategic-partner' explicitly; the skill is the brake.

驗證： ls ~/.claude/skills/strategic-partner/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives activation.

驗證： head ~/.claude/skills/strategic-partner/SKILL.md

Wrong trigger keywords — no premise challenge happens

Phrase as 'challenge my premise' or 'advisor mode' explicitly; 'help me build X' skips advisory.

替代方案

strategic-partner 對比其他方案

替代方案	何時用它替代	權衡
planning-with-files	You want disk-based progress memory rather than decision gating	Complementary — different purposes
Carmack Council	You want multi-expert review rather than chief-of-staff persona	Different phase — Council reviews, SP decides upstream

strategic-partner