What problem does it solve?
After a multi-provider council run finishes, its raw artifacts (summary.json and per-seat verdict files) are hard to act on. This Skill reads those artifacts and explains what the verdicts actually mean before anyone makes a decision based on them.
Core Features & Use Cases
- Artifact Location and Validation: Finds the newest council output under ~/.claude-octopus/results/ and confirms each seat's real provider and model, flagging same-lineage panels that weaken verdict independence.
- Verdict Tallying and Quorum Checks: Counts APPROVE, REJECT, ABSTAIN, and REVISE votes, treats malformed verdicts as abstentions, and checks the SubagentStop gate's quality scores.
- Dissent Analysis and Action Mapping: Quotes the strongest dissenting argument verbatim and maps the tally to a concrete next step, such as proceeding, proceeding with follow-ups, or re-running.
- Use Case: After a /octo:council run on an architecture decision, ask what the council decided and receive a plain-language verdict summary with quorum status, dissent highlights, and a recommended action.
Quick Start
Ask the assistant to interpret the latest council run results and explain what the verdicts mean for your pending decision.