Skip to content

hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/council

council

Verified

Compare independent opinions from models or contexts without inflating agreement. Use when: wanting several opinions or a debate, or summarizing several reviewers' results.

FileKindSize
SKILL.mdskill md12.2 KB
references/debate.mdmarkdown3.8 KB
references/duel.mdmarkdown1.2 KB
references/interview-panel.mdmarkdown1.4 KB
references/judge-split.mdmarkdown1.4 KB
schemas/council-report.v1.schema.jsonconfig4.7 KB
scripts/validate-output.shexecutablescript4.3 KB
scripts/validate.shexecutablescript4.6 KB

references/interview-panel.md

View on GitHub
# Interview panel: the council answers an Interview

Loaded by [Council](../SKILL.md) when the caller asks a council to answer an
[Interview](../../interview/SKILL.md).

Interview is human-invoked. When the caller asks a council to answer it,
Interview still asks one question at a time and Council stands in as answerer.

1. Send each choice question to every member in a fresh sealed context with
   the same evidence; fact questions stay with the caller. Only the synthesized
   answers to earlier questions travel, labeled provisional, never a peer's raw
   answer. Each member returns an answer in Interview's shape: recommendation,
   reason, and tradeoff.
2. Mark answers the members agree on as **council-agreed**. Keep divergent
   answers open, each position with its evidence.
3. After the question set, or at Interview's stop condition, run one bounded
   debate on the open disagreements under the [debate](debate.md) rules. Vote
   on an exact candidate only if the caller chose a majority rule.
4. Return the synthesized answers with dissent. The caller accepts or amends
   them in one pass before Interview records anything.

The council may recommend authority, budgets, Git or external write
permission, and acceptance changes to a running goal. It never grants or makes
them; those answers stay the caller's even in this mode.

It's working if nothing reaches Interview before the caller accepts it.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall