/ 디렉터리 / 플레이그라운드 / strategic-partner
● 커뮤니티 JimmySadek ⚡ 바로 사용

strategic-partner

제작: JimmySadek · JimmySadek/strategic-partner

Chief-of-Staff skill for Claude Code — separates deciding from building. Challenges assumptions, forces Path A/B/C, gates before implementation.

JimmySadek/strategic-partner makes Claude act as an advisory persona rather than an executor. Two-session loop: an Advisory session (persistent) interrogates assumptions, presents Path A/B/C with tradeoffs, routes tasks, and keeps decision history — while Execution sessions (ephemeral) receive self-contained prompts and build with clean context. Key gates: premise challenge (4 trigger conditions), forced alternatives (3 paths), confidence labels ([SAFE] / [RISK]), Advisory Completion Gate (5 conditions), 14 named cognitive patterns. Core principle: 'The SP never builds. The executor never decides.'

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

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
흐름
  1. 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
  2. Receive Path A/B/C
    Give me three paths with tradeoffs.✓ 복사됨
    → Three distinct paths, each labeled [SAFE] or [RISK], with honest downsides
  3. 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
  4. 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.

흐름
  1. 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
  2. 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와 조합해 10배 효율

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 0
forced_alternatives problem statement Once premise passes; before committing to one path 0
completion_gate chosen path + context Before crafting executor prompt 0
executor_prompt_craft decision + context Handoff to execution 0
decision_log current session state Throughout advisory session 0

비용 및 제한

운영 비용

API 쿼터
None
호출당 토큰
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

문제 해결

자주 발생하는 오류와 해결

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-filesYou want disk-based progress memory rather than decision gatingComplementary — different purposes
Carmack CouncilYou want multi-expert review rather than chief-of-staff personaDifferent phase — Council reviews, SP decides upstream

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기