Loop council
Skill cbdreamer11/CB-loop-kit-claude-plugin/skills/loop-council
A session-based working method for coding agents: plan in thin complete slices, build one at a time, verify by observing real behaviour, hand off cleanly. Skills + agents + 2 hooks for Claude Code.
npx -y skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loop-councilAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Sends an open design question to several independent voices in parallel and returns a decision with its evidence. Use before building anything that touches money, permissions, auth, or schema, or whenever the honest answer is "I am not sure".
SKILL.md
2.3 KB, 461 tokens by cl100k_base, as published. Nobody here has run it
Council
A council exists so that a decision is made against reality instead of against recollection. It runs before the code, not as a review afterwards.
When it is required (not optional)
Look at what the change will touch — not at how confident you feel, because self-reported confidence is exactly the thing that fails:
- money, pricing, refunds, anything that charges someone
- permissions, authentication, or who can see whose data
- database schema, migrations, or anything that is hard to undo
- a public contract other code depends on
Two voices minimum. Three when it touches money, permissions, or schema.
The voices
Dispatch them in one message so they run in parallel, each blind to the others:
loop-planner— the architecture: the shape, the alternatives, what breaks later.loop-domain— the facts: decides against real documentation and the real installed behaviour, with URLs or exact strings. Never from memory.loop-auditor— the red team: its only job is to refute the proposed design before it exists. Give it the proposal, and tell it to assume there is a hole.
Resolving it
- Have each voice write its verdict to
.loop/council/<topic>-<voice>.mdas it finishes. Councils get interrupted; a verdict only in context is a verdict lost, and you should be able to resume without re-running the ones that finished. - If the red team and the architect disagree, the red team wins by default — or it escalates to the owner if it is really a business call. Never split the difference into something neither voice endorsed.
- Write the outcome into
.loop/DECISIONS.md: the decision, the alternative that was rejected and why, and the evidence. The rejected alternative is the part future sessions will need most.
What a council is not
It is not a vote to feel better about a decision already made, and it is not a substitute for reading the code. If the question can be answered by opening a file, open the file.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.