strategic-partner MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

strategic-partner-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: 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

Wann einsetzen: You're about to ask Claude Code to build something substantial. Pause and consult the advisor first.

Voraussetzungen

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

Ablauf

Open the advisory session

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

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

Give me three paths with tradeoffs.✓ Kopiert

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

I pick Path B. Prepare the executor prompt.✓ Kopiert

→ 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.✓ Kopiert

→ Execution session works with clean context

Ergebnis: Work that's been decided deliberately rather than drifted into.

Fallstricke

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

Kombinieren mit: github

Run a weekly strategy review with the persistent advisor

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

Wann einsetzen: Friday afternoon, closing out the week.

Ablauf

Review decisions made this week

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

→ 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?✓ Kopiert

→ Pinpoint rather than a to-do list

Ergebnis: A weekly audit that compounds across months.

Kombinieren mit: planning-with-files

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: Advisor sessions carry persistent context — can grow
Kosten in €: Free — skills are local files
Tipp: Trim the decision log periodically; stale decisions bloat context.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — pure prompts

Datenabfluss: None

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

Fehlerbehebung

Häufige Fehler und Lösungen

Skill not invoked — Claude jumps to building

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

Prüfen: ls ~/.claude/skills/strategic-partner/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives activation.

Prüfen: 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.

Alternativen

strategic-partner vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen