Carmack-Council MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

10 named experts with opinionated philosophies, not generic review prompts
Parallel subagents — each expert gets its own 200k context window
Chair orchestrator merges and prioritizes findings across experts
Four-stage workflow (spec / plan / implement / review) with feedback loops
Scales to large codebases because no single context must hold everything

라이브 데모

실제 사용 모습

carmack-council-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "carmack-council-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "carmack-council-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/SamJHudson01/Carmack-Council",
          "~/.claude/skills/Carmack-Council"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add carmack-council-skill -- git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: Carmack-Council

Get a 10-expert review on a PR before you merge it

👤 Engineers on small teams without a deep review bench ⏱ ~30 min intermediate

언제 쓸까: You'd like a security person, a perf person, a testing person to look at your PR — but there's just you.

사전 조건

Skill cloned — git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council

흐름

Invoke the review stage

Carmack Council review: PR <link or diff>. Dispatch all experts.✓ 복사됨

→ Ten parallel reviews running, each domain-scoped
Read the merged report

Summarize the top 3 issues across all experts, ordered by severity.✓ 복사됨

→ Prioritized, not 10 disjoint reports
Fix and re-review

I fixed 1 and 2. Re-review with just Troy Hunt and Brandur for issue 3.✓ 복사됨

→ Focused re-review, not full re-dispatch

결과: A PR that's survived 10 expert lenses — stronger than a rubber stamp from a teammate.

함정

Experts disagree — The Chair merges and prioritizes — if two experts conflict, pick the one your situation weights heavier

함께 쓰기: github

Run a feature through the full spec → plan → implement → review pipeline

👤 Small teams building a feature end-to-end with AI ⏱ ~120 min advanced

언제 쓸까: Feature is substantial and you want structured gates.

흐름

Spec

Carmack Council: spec for adding Stripe-based subscriptions.✓ 복사됨

→ Carmack-opinionated spec — pragmatic, not architecture-astronautic
Plan + implement

Proceed to plan, then implement in the smallest vertical slice.✓ 복사됨

→ Thin working slice, not a scaffolding swamp
Council review

Review with all 10 experts.✓ 복사됨

→ Cross-domain findings tied to actual lines

결과: A feature shipped with a thoroughly reviewed implementation.

함정

You treat expert style as gospel — They're opinions backed by real engineers' writing — they're evidence, not commandments

함께 쓰기: github · planning-with-files

조합

다른 MCP와 조합해 10배 효율

carmack-council-skill + github

Run council_review against a real PR, post summary as a PR comment

Council review PR #47; post the prioritized top-5 as a comment.✓ 복사됨

carmack-council-skill + planning-with-files

Track council findings across multiple review rounds

Use planning-with-files progress.md to track which council findings are resolved.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
spec_stage	feature intent	Start of a feature	0
plan_stage	approved spec	After spec	0
implement_stage	approved plan	Actually building	0
council_review	diff or PR	Before merge	High — 10 parallel agents
single_expert_review	diff + expert name	Re-check a specific concern after fix	1/10 of full council

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: High — council_review runs 10 parallel agents
금액: Free — skills are local files. LLM token cost scales with parallelism.
팁: Use single_expert_review for targeted re-checks; full council is expensive per run.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials — pure prompts

데이터 외부 송신: None — all review happens in-session

문제 해결

자주 발생하는 오류와 해결

Skill not invoked — Claude does a regular review

Say 'Carmack Council review' explicitly.

확인: ls ~/.claude/skills/Carmack-Council/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives dispatch logic.

확인: head ~/.claude/skills/Carmack-Council/SKILL.md

Wrong trigger keywords — only one expert activates

Say 'dispatch all experts' or 'full council' explicitly.

대안

Carmack-Council 다른 것과 비교

대안	언제 쓰나	단점/장점
Single-reviewer vanilla Claude	Small changes where 10 experts is overkill	Cheaper, less coverage
Human code review	Team has real reviewers	Better but slower — Council complements, doesn't replace

Carmack-Council