strategic-partner MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

strategic-partner-skill.replay ▶ prêt

0/0

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la 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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

Quand l'utiliser : You're about to ask Claude Code to build something substantial. Pause and consult the advisor first.

Prérequis

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

Déroulement

Open the advisory session

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

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

Give me three paths with tradeoffs.✓ Copié

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

I pick Path B. Prepare the executor prompt.✓ Copié

→ 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.✓ Copié

→ Execution session works with clean context

Résultat : Work that's been decided deliberately rather than drifted into.

Pièges

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

Combiner avec : github

Run a weekly strategy review with the persistent advisor

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

Quand l'utiliser : Friday afternoon, closing out the week.

Déroulement

Review decisions made this week

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

→ 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?✓ Copié

→ Pinpoint rather than a to-do list

Résultat : A weekly audit that compounds across months.

Combiner avec : planning-with-files

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
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

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Advisor sessions carry persistent context — can grow
Monétaire: Free — skills are local files
Astuce: Trim the decision log periodically; stale decisions bloat context.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — pure prompts

Sortie de données : None

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

Dépannage

Erreurs courantes et correctifs

Skill not invoked — Claude jumps to building

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

Vérifier : ls ~/.claude/skills/strategic-partner/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives activation.

Vérifier : 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.

Alternatives

strategic-partner vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills