/ Directorio / Playground / Carmack-Council
← Todos los servidores ↗ GitHub
● Comunidad 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 qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

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

Instalar

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

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.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 el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la 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
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "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
    }
  }
}

Mismo formato que Claude Desktop. Reinicia 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"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del 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

Cuándo usarlo: You'd like a security person, a perf person, a testing person to look at your PR — but there's just you.

Requisitos previos
  • Skill cloned — git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council
Flujo
  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.

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

Cuándo usarlo: Feature is substantial and you want structured gates.

Flujo
  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.

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

Combinaciones

Combínalo con otros MCPs para multiplicar por 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.✓ 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

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None
Tokens por llamada
High — council_review runs 10 parallel agents
Monetario
Free — skills are local files. LLM token cost scales with parallelism.
Consejo
Use single_expert_review for targeted re-checks; full council is expensive per run.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials — pure prompts
Salida de datos: None — all review happens in-session

Resolución de problemas

Errores comunes y soluciones

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 otros

AlternativaCuándo usarlaContrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills