# Council

> Explore a codebase with parallel agents, then hand off findings. Use when the user types /council.

- Skill: `blockmatic/council` (Agent Skill)
- Install (CLI): `npx skillmds@latest add blockmatic/council`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blockmatic/council/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: blockmatic (https://skillmd.com/u/blockmatic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/blockmatic/council

---


## Purpose and inputs

Gather architecture and keywords for the requested area, then spawn a small set of varied explorers. This playbook inspects. It does not commit, push, or open a PR. Implementation continues only when the user already asked for it.

## Steps

1. Inspect the area yourself first: owning packages, README/scripts, and current behavior. Record keywords and the architecture sketch the agents will use.
2. Spawn explorers only as needed. Default to 3; the user may raise the count up to 6. Six is a hard maximum even if they request more — split larger investigations into separate bounded runs. Give each a distinct angle; include one out-of-the-box probe.
3. Reconcile reports against the tree. Prefer file evidence over agent summaries. If the working tree changed underfoot, re-verify before using a finding.
4. If the user asked only to investigate or plan, hand off. If they also asked to implement, follow [build](../build/SKILL.md) after the inspection — do not publish.

## Verification

- [ ] Findings cite paths that still exist.
- [ ] No Git publish happened from this playbook.
- [ ] Implementation, if any, was already authorized by the user.

## Handoff

Return a short evidence list, contradictions, and the next named playbook (`/plan-feature`, `/build`, or stop). For plans, include References, 3–5 assumptions, and deferrals per [plan-feature](../plan-feature/SKILL.md).