/ Annuaire / Playground / Carmack-Council
← Tous les serveurs ↗ GitHub
● Communauté SamJHudson01 ⚡ Instantané

Carmack-Council

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

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

carmack-council-skill.replay ▶ prêt
0/0

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la 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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

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

Continue utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

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

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

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

Pièges
  • Experts disagree — The Chair merges and prioritizes — if two experts conflict, pick the one your situation weights heavier
Combiner avec : 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

Quand l'utiliser : Feature is substantial and you want structured gates.

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

Résultat : A feature shipped with a thoroughly reviewed implementation.

Pièges
  • You treat expert style as gospel — They're opinions backed by real engineers' writing — they're evidence, not commandments
Combiner avec : github · planning-with-files

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
High — council_review runs 10 parallel agents
Monétaire
Free — skills are local files. LLM token cost scales with parallelism.
Astuce
Use single_expert_review for targeted re-checks; full council is expensive per run.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — pure prompts
Sortie de données : None — all review happens in-session

Dépannage

Erreurs courantes et correctifs

Skill not invoked — Claude does a regular review

Say 'Carmack Council review' explicitly.

Vérifier : ls ~/.claude/skills/Carmack-Council/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives dispatch logic.

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

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

Alternatives

Carmack-Council vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills