speckit-council

Orchestrates a multi-agent adversarial council that reviews a feature plan before implementation.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-council-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-council
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-council
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-council-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans written by a single AI session often carry unchallenged assumptions and blind spots. This Skill convenes an adversarial review council over a spec-kit feature's plan.md so design flaws are caught before any code is written or tokens are spent on implementation. ## Core Features & Use Cases - Multi-agent plan defense: Dispatches a configurable bench of 1-8 Sonnet reviewer agents (each with a distinct lens like correctness, risk, simplicity, testability, sequencing) to produce independent opinions in parallel, followed by anonymized peer review and an Opus chairman synthesis. - Tiered ceremony and cost control: Supports full and standard council tiers via profile.yaml, scaling session counts, context loading (eager vs lazy), output caps, and graph-query ceilings to balance review depth against token cost. - Resumable, auditable rounds: Writes classified suggestions to council/round-N/suggestions.md with stable finding IDs, per-session traces, graphify grounding checks, and support for --reopen delta or full to re-review revised plans. - Use Case: After running /speckit-plan on a new feature, invoke /speckit-council to have five independent reviewers attack the plan, then feed the resulting suggestions.md into /speckit-council-triage before writing tasks. ## Quick Start Run /speckit-council in a spec-kit repository with a completed plan.md to convene the plan-defense council and generate a classified suggestions report for the current feature.

Frequently Asked Questions about speckit-council

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial review on a spec-kit plan?

Invoke /speckit-council inside a spec-kit repository after plan.md exists. The skill dispatches parallel reviewer agents with distinct lenses, runs a peer-review stage, and an Opus chairman synthesizes everything into council/round-N/suggestions.md.

How do I change the number of council reviewers?

Set council_members (1-8) in the feature's profile.yaml to override the repo-wide member_count default of 5 in council-config.yml. A bench of 1 skips peer review entirely and records why in the chairman's note.

What is the difference between full and standard council tiers?

The full tier runs one peer-review session per member with eager context loading and no output cap (12 sessions at default size). The standard tier uses one consolidated peer-critique session, lazy context loading, and output caps (8 sessions at default size).

Does the council work without a graphify dependency graph?

Yes. If graphify-out/graph.json is absent, the council degrades to a flagged deck-only review rather than blocking, and the reduced-grounding status is surfaced in the chairman's suggestions.md banner.

Can I re-run the council on a plan that was already defended?

Yes, use --reopen delta with a triggering finding to re-review only the changed plan diff, or --reopen full to convene a complete fresh round. Completed rounds are never overwritten; each run creates round N+1.

What happens if a council run is interrupted mid-review?

The skill resumes the interrupted round in place: it skips deck-prep and any stage whose artifacts already exist on disk, continuing from the first incomplete stage without re-running finished work.