/ Verzeichnis / Playground / Carmack-Council
← Alle Server ↗ GitHub
● Community SamJHudson01 ⚡ Sofort

Carmack-Council

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

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

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

Installieren

Wählen Sie Ihren Client

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

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer 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"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: 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

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

Voraussetzungen
  • Skill cloned — git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council
Ablauf
  1. Invoke the review stage
    Carmack Council review: PR <link or diff>. Dispatch all experts.✓ Kopiert
    → Ten parallel reviews running, each domain-scoped
  2. Read the merged report
    Summarize the top 3 issues across all experts, ordered by severity.✓ Kopiert
    → 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.✓ Kopiert
    → Focused re-review, not full re-dispatch

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

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

Wann einsetzen: Feature is substantial and you want structured gates.

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

Ergebnis: A feature shipped with a thoroughly reviewed implementation.

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
High — council_review runs 10 parallel agents
Kosten in €
Free — skills are local files. LLM token cost scales with parallelism.
Tipp
Use single_expert_review for targeted re-checks; full council is expensive per run.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — pure prompts
Datenabfluss: None — all review happens in-session

Fehlerbehebung

Häufige Fehler und Lösungen

Skill not invoked — Claude does a regular review

Say 'Carmack Council review' explicitly.

Prüfen: ls ~/.claude/skills/Carmack-Council/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives dispatch logic.

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

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

Alternativen

Carmack-Council vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen