skills/council-review/SKILL.md
Multi-model validation council — auto-validate plans, architecture changes, and PRs via validate-plan/review before executing
npx skillsauth add alinaqi/claude-bootstrap council-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When you write a plan to ~/.claude/plans/, automatically validate it:
~/bin/validate-plan --threshold 2 ~/.claude/plans/<plan-file>.md
When making architectural changes (new services, API redesigns, database schema changes), run:
~/bin/review --all "Review this architecture: <summary>"
Before marking a PR as done, run:
~/bin/review --all --file <changed-files>
Council behavior is configured in ~/.claude/council.yaml. The Maggy dashboard (Settings > Council) also manages this config.
chief: claude-fable-5 — Claude Fable 5 (Anthropic's most capable widely-released
model, GA 2026-06-09) leads every panel as the chief: it reviews first and casts
the deciding synthesis. Invoked via ~/bin/claude-fable-5. Override the chief in
~/.claude/council.yaml.
The chief leads each context, followed by the panel:
| Context | Default Reviewers | When |
|---------|-------------------|------|
| plan | Claude Fable 5 (chief), DeepSeek Pro, Codex, Gemini Pro | Before executing any plan |
| review | Claude Fable 5 (chief), DeepSeek Pro, Kimi | Code review, PR review |
| architecture | Claude Fable 5 (chief), DeepSeek Pro, Gemini Pro, Grok | System design, schema changes |
The threshold setting controls how many approvals are needed:
threshold: 2 with 3 reviewers → need 2/3 to auto-executeAll 13 tiers are listed in ~/.claude/council.yaml under models:. Each has:
id — unique identifiercmd — CLI command to invoke (null for Claude models, which are the host)tier — routing priority (0=cheapest, 12=most capable)label — human-readable nameUse POST /api/models/health to verify all models are responding.
This skill is loaded by Claude Code on session start. It provides the behavioral rules for when to invoke multi-model validation. The actual execution happens via ~/bin/validate-plan and ~/bin/review which are already installed.
Do not skip council validation for CLAUDE-tier tasks. The whole point is that architecture and security decisions get independent verification before execution.
development
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies
development
Mandatory code reviews via /code-review before commits and deploys
development
# Visual Validation — Autonomous Screenshot Verification ## Philosophy Every UI change should be visually verified before it ships. Peekaboo captures pixel-accurate screenshots. The system compares before/after and flags visual regressions. No manual "looks good to me" — the machine verifies what the machine built. ## Autonomous Flow ``` static/* files modified (detected by auto-review-hook or E2E testkit) ↓ peekaboo image --mode screen → ~/.maggy/visual-verify/after-{ts}.png ↓ Compa
tools
# Model Routing System ## How Routing Decisions Are Made Every user prompt goes through a 9-tier classification pipeline before any AI model processes it. The system answers three questions: 1. **Which model should handle this?** — 9-tier cost/complexity classification 2. **Is the classifier itself working?** — Cascading fallback (qwen3 → kimi → deepseek → cache) 3. **Can we verify the result?** — Tool-level fallback + auto-evaluation ### The Pipeline ``` User types prompt ↓ UserPromptS