Skill not invoked — Claude jumps to building

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

SKILL.md frontmatter wrong

Re-clone; description drives activation.

strategic-partner (Claude Skill) — 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: 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.

흐름

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와 조합해 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
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
호출당 토큰: 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.

문제 해결

자주 발생하는 오류와 해결

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