/ Diretório / Playground / Carmack-Council
← Todos os servidores ↗ GitHub
● Comunidade SamJHudson01 ⚡ Instantâneo

Carmack-Council

por SamJHudson01 · SamJHudson01/Carmack-Council

Multi-agent Claude Code framework: 10 expert sub-agents (Carmack, Fowler, Kent Beck, Troy Hunt...) each review code in parallel with their own 200k context.

The Carmack Council structures development as spec → plan → implementation → review, with feedback loops. The headline innovation is parallel expert subagents: the Chair orchestrator dispatches 10 specialists simultaneously (Carmack engineering, Fowler refactoring, Kent Beck testing, Troy Hunt security, Matteo Collina backend, Brandur Postgres, Vercel perf, Simon Willison LLMs, Karri Saarinen UI, Vitaly Friedman UX). Each gets its own 200k context for its domain.

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

carmack-council-skill.replay ▶ pronto
0/0

Instalar

Escolha seu cliente

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.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 usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "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
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

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

O Continue usa um array de objetos de servidor em vez de um map.

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: 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

Quando usar: You'd like a security person, a perf person, a testing person to look at your PR — but there's just you.

Pré-requisitos
  • Skill cloned — git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council
Fluxo
  1. Invoke the review stage
    Carmack Council review: PR <link or diff>. Dispatch all experts.✓ Copiado
    → Ten parallel reviews running, each domain-scoped
  2. Read the merged report
    Summarize the top 3 issues across all experts, ordered by severity.✓ Copiado
    → Prioritized, not 10 disjoint reports
  3. Fix and re-review
    I fixed 1 and 2. Re-review with just Troy Hunt and Brandur for issue 3.✓ Copiado
    → Focused re-review, not full re-dispatch

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

Armadilhas
  • Experts disagree — The Chair merges and prioritizes — if two experts conflict, pick the one your situation weights heavier
Combine com: 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

Quando usar: Feature is substantial and you want structured gates.

Fluxo
  1. Spec
    Carmack Council: spec for adding Stripe-based subscriptions.✓ Copiado
    → Carmack-opinionated spec — pragmatic, not architecture-astronautic
  2. Plan + implement
    Proceed to plan, then implement in the smallest vertical slice.✓ Copiado
    → Thin working slice, not a scaffolding swamp
  3. Council review
    Review with all 10 experts.✓ Copiado
    → Cross-domain findings tied to actual lines

Resultado: A feature shipped with a thoroughly reviewed implementation.

Armadilhas
  • You treat expert style as gospel — They're opinions backed by real engineers' writing — they're evidence, not commandments
Combine com: github · planning-with-files

Combinações

Combine com outros MCPs para 10× de alavancagem

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

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
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

Custo e limites

O que custa rodar

Cota de API
None
Tokens por chamada
High — council_review runs 10 parallel agents
Monetário
Free — skills are local files. LLM token cost scales with parallelism.
Dica
Use single_expert_review for targeted re-checks; full council is expensive per run.

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: No credentials — pure prompts
Saída de dados: None — all review happens in-session

Solução de problemas

Erros comuns e correções

Skill not invoked — Claude does a regular review

Say 'Carmack Council review' explicitly.

Verificar: ls ~/.claude/skills/Carmack-Council/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives dispatch logic.

Verificar: head ~/.claude/skills/Carmack-Council/SKILL.md
Wrong trigger keywords — only one expert activates

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

Alternativas

Carmack-Council vs. outros

AlternativaQuando usarTroca
Single-reviewer vanilla ClaudeSmall changes where 10 experts is overkillCheaper, less coverage
Human code reviewTeam has real reviewersBetter but slower — Council complements, doesn't replace

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills