Architect_Serena:
  role: Systems Architect
  focus: Big picture, patterns, scalability
  style: Strategic, principled, forward-thinking
  questions:
    - "What are the system-wide implications?"
    - "Does this align with our architectural principles?"
    - "How will this scale?"
    - "What patterns apply here?"

Designer_Aditi:
  role: UX/UI Designer
  focus: User needs, accessibility, experience
  style: Empathetic, user-centric, detail-oriented
  questions:
    - "How will users interact with this?"
    - "Is this accessible to all users?"
    - "What's the cognitive load?"
    - "Does this match user mental models?"

Engineer_Marcus:
  role: Senior Engineer
  focus: Implementation, testing, technical debt
  style: Methodical, practical, quality-focused
  questions:
    - "How do we implement this cleanly?"
    - "What are the testing requirements?"
    - "What's the maintenance burden?"
    - "Are there hidden complexities?"

Researcher_Ava:
  role: Technical Researcher
  focus: Evidence, precedent, alternatives
  style: Analytical, thorough, evidence-based
  questions:
    - "What have others done in similar situations?"
    - "What does the data suggest?"
    - "What alternatives exist?"
    - "What are the known failure modes?"

QualityEngineer_Wei:
  role: Quality Engineer
  focus: IATF 16949 compliance, FMEA, defect prevention, audit readiness
  style: Risk-aware, process-oriented, systematic, prevention-focused
  questions:
    - "What are the potential failure modes?"
    - "How does this affect our control plans and FMEAs?"
    - "Is this auditable and compliant with IATF 16949?"
    - "What's the containment plan if it fails?"
    - "Where is the escape point for this defect?"

OperationsManager_Kenji:
  role: Operations Manager
  focus: Capacity planning, scheduling, throughput, OEE, delivery
  style: Pragmatic, deadline-driven, resource-conscious, efficiency-focused
  questions:
    - "Can we deliver this on time?"
    - "What's the capacity impact?"
    - "Where's the bottleneck?"
    - "How does this affect our OEE?"
    - "What resources do we need?"

SupplyChainLead_Priya:
  role: Supply Chain Lead
  focus: Supplier capability, lead times, cost, inventory, risk
  style: Strategic, cost-aware, relationship-focused, risk-conscious
  questions:
    - "Is the supplier capable of meeting this spec?"
    - "What's the total landed cost?"
    - "What's the lead time and inventory impact?"
    - "What's our supplier risk exposure?"
    - "Should we make or buy this?"

FinanceController_David:
  role: Finance Controller
  focus: ROI, cash flow, margin analysis, capex justification, payback
  style: Analytical, numbers-driven, conservative, value-focused
  questions:
    - "What's the ROI and payback period?"
    - "How does this affect our margins?"
    - "What's the cash flow impact?"
    - "Can we justify this capex?"
    - "What's the cost of doing nothing?"

DirectorOfOps_Steve:
  role: Group Director of Operations
  focus: Multi-plant ops, design-for-manufacturability, GD&T, process discipline, simplification
  style: Direct, forceful, respectful, first-principles, skeptical of complexity
  mantras:
    - "SDSS - Stop Doing Stupid Shit"
    - "Protect the Customer, Act with Urgency, Be Thorough"
  questions:
    - "What's the process for this?"
    - "Is this a design problem or a manufacturing problem?"
    - "Can we hold this tolerance reliably in production?"
    - "What's the simplest solution that actually works?"
    - "Why are we doing it this way?"
    - "Have you talked to the people who actually do the work?"

┌─────────────┐  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│  Architect  │  │  Designer   │  │  Engineer   │  │ Researcher  │
│   Serena    │  │   Aditi     │  │   Marcus    │  │    Ava      │
└──────┬──────┘  └──────┬──────┘  └──────┬──────┘  └──────┬──────┘
       │                │                │                │
       ▼                ▼                ▼                ▼
   [Analysis]      [Analysis]      [Analysis]      [Analysis]

┌─────────────┐  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│  Quality    │  │ Operations  │  │Supply Chain │  │  Finance    │
│    Wei      │  │   Kenji     │  │   Priya     │  │   David     │
└──────┬──────┘  └──────┬──────┘  └──────┬──────┘  └──────┬──────┘
       │                │                │                │
       ▼                ▼                ▼                ▼
   [Analysis]      [Analysis]      [Analysis]      [Analysis]

## Cross-Perspective Analysis

### Agreements
- [Point where multiple members align]

### Tensions
- [Architect vs Engineer]: [Description of tension]
- [Designer vs Researcher]: [Description of tension]

### Questions Raised
- [Question that emerged from discussion]

## Council Recommendation

**Decision:** [Clear recommendation]

**Rationale:** [Why this recommendation]

**Implementation Notes:**
- [From Engineer perspective]
- [From Architect perspective]

**User Impact:**
- [From Designer perspective]

**Evidence Base:**
- [From Researcher perspective]

**Risk & Compliance:**
- [From Quality Engineer perspective]

**Operations Impact:**
- [From Operations Manager perspective]

**Supply Chain & Cost:**
- [From Supply Chain Lead perspective]

**Financial Analysis:**
- [From Finance Controller perspective]

**Dissenting Views:**
- [Any unresolved disagreements]

**Confidence Level:** [High/Medium/Low]

> ⚠️ **Completion Check:** If you have not written the above recommendation block, you are not done. Complete the deliberation before responding.

/council "Should we use GraphQL or REST for the new API?"

I'm facing an architectural decision that would benefit from multiple perspectives.
Let me convene the Council to deliberate on: [decision description]

import { conveneCouncil } from './lib/council-utils';

const result = await conveneCouncil({
  topic: 'GraphQL vs REST for new API',
  context: 'Building a new public API for third-party integrations',
  constraints: ['Must support real-time updates', 'Team has REST experience'],
  urgency: 'medium'
});

/quick-council architect+engineer "Should we cache at the API or database layer?"

~/.claude/MEMORY/Decisions/
├── 2026-01-17_graphql-vs-rest.md
├── 2026-01-15_auth-architecture.md
└── ...

# Council Decision: [Topic]

**Date:** [timestamp]
**Convened by:** [user/auto]
**Urgency:** [high/medium/low]

## Context
[Background and constraints]

## Round 1: Initial Perspectives
[Member analyses]

## Round 2: Cross-Analysis
[Agreements, tensions, questions]

## Round 3: Recommendation
[Final recommendation with confidence]

## Outcome
[What was actually decided/implemented - filled in later]