About w-council
w-council is an investigation playbook for exploring an area of a codebase with a small set of read-only agents. It gathers architectural context and evidence, then reconciles findings without making changes or publishing.
Key features
- 01Inspect packages, documentation, and scripts
- 02Record keywords and architecture
- 03Delegate bounded read-only investigations
- 04Request file-and-line evidence
- 05Reconcile reports against the codebase
- 06Stop before implementation or publishing
Use cases
- 01Explore an unfamiliar codebase area
- 02Gather evidence for an architecture question
- 03Compare independent investigation reports
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ blockmatic/ basilic-skills --skill w-councilAfter installing, type/w-councilin Claude Code to confirm it loaded.
Details
From the project READMEGather 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.
- Inspect the area yourself first: owning packages, README/scripts, and current behavior. Record keywords and the architecture sketch the agents will use. Skip spawn when one targeted read answers the question.
- Spawn explorers only as needed. Default to 2–3 with distinct angles, including one out-of-the-box probe. Each brief is self-contained: roots, keywords, sketch, read-only, file:line evidence, no fixes, no further spawn. Split larger investigations into separate bounded runs.
- Reconcile reports against the tree. Prefer file evidence over agent summaries. If the working tree changed underfoot, re-verify before using a finding.
- Investigate-only: stop after reconcile. Plan: emit plan output in this turn. Follow build only if they already asked to implement — do not publish.
Comments
Markdown supported