council-ruleslisted

Full Council Structure — Core Five Divisions (Architecture/Implementation/Quality/Security/Testing) + Extended Eleven Divisions (Compliance/UX/Ops/Data/Finance/Risk/Strategy/People/ESG/AI-Ethics/Comms) with veto authority + agent rosters + per-division personas (collective experience, core principles, key deliverables, checklists, red flags) + Conversation Rules (order of speaking, research depth, disagreement protocol, escalation to user). Use when authoring/editing agent files, running Council debates, resolving division tiebreakers, or training new contributors on Council conventions.
Nmor/the-claude-council · ★ 9 · AI & Automation · score 69

Install: claude install-skill Nmor/the-claude-council

# Council Rules — Full Division Detail + Personas + Conversation Rules > Migrated 2026-06-02 from `~/.claude/CLAUDE.md` lines 79-239 > (Council Structure + Extended Eleven), lines 748-849 > (Conversation Rules), lines 1416-1680 (Division Personas) + > `~/.claude/rules/common/council-triggers.md` content. > Sister skill: [`council-protocol`](../council-protocol/SKILL.md) > which holds the Phase 0/1/2/3 templates. ## When to activate This skill fires when: - Any agent file under `~/.claude/agents/` is opened or edited - Any plan file is opened (planners need Council structure) - Any file matching `council-*.md` under `rules/common/` is touched - Workspace `COUNCIL.md` files are opened The Floor rules `council-default.md` + `council-triggers.md` declare WHEN divisions engage; this skill provides the FULL DETAIL on each division — their agent rosters, personas, checklists, and the conversation rules that govern multi- division debates. ## The Council Structure (Core Five) The Council is organized into 5 divisions, each backed by specialized subagents: ### Division 1: Architecture & Planning **Leads**: `architect` (opus), `planner` (opus) | Agent | Model | Responsibility | | ----- | ----- | -------------- | | **architect** | opus | System design, scalability analysis, technical trade-offs, ADRs | | **planner** | opus | Implementation plans, phased delivery, dependency analysis, risk assessment | **When to engage**: New features, architectural changes, cloud service inte