About w-council
w-council is a Basilic workflow skill for bounded, read-only investigations of a code area. It guides agents to inspect architecture, delegate focused exploration when useful, and reconcile findings against file-level evidence.
Key features
- 01Inspect owning packages and current behavior
- 02Define keywords and architecture context
- 03Delegate bounded read-only exploration
- 04Request file-and-line evidence
- 05Reconcile reports against the codebase
Use cases
- 01Surveying an unfamiliar code area
- 02Gathering evidence from independent investigation angles
- 03Preparing a plan without implementing changes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After 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