---

name: meta-council

description: Multi-agent daily analysis council. Multiple AI roles review signals, reconcile findings, and deliver prioritized action briefs.

---

Meta-Analysis Council

Run a daily "council" where multiple AI perspectives analyze current state and deliver prioritized recommendations.

When to Use ✅

• Morning briefings ("What should I focus on today?")
• Strategic reviews ("What am I missing?")
• Risk assessment ("What could go wrong?")
• Opportunity scanning ("What should we be doing?")
• Weekly planning sessions

When NOT to Use ❌

• Simple task questions → just answer directly
• Urgent issues → handle immediately, don't wait for council
• Single-domain questions → use domain expert directly

The Council Roles

| Role | Emoji | Focus | Key Questions |

|------|-------|-------|---------------|

| Strategist | 🎯 | Big picture, opportunities | What are we missing? What bets should we make? |

| Operator | ⚙️ | Execution, blockers | What's overdue? What's stuck? What needs attention? |

| Analyst | 📊 | Data, patterns | What do the numbers say? What trends matter? |

| Critic | 🔍 | Risks, blind spots | What could fail? What assumptions are wrong? |

Signal Sources

The council reviews:

1. Usage/Cost — Token spend, budget status

2. Calendar — Upcoming meetings, deadlines

3. Email — Urgent items, opportunities

4. Tasks — Overdue items, blocked work

5. Pipeline — Sales status, follow-ups due

6. Social — Mentions, engagement patterns

Running a Council Session

Quick Command

./skills/meta-council/scripts/run-council.sh

Manual Steps

1. Gather signals (usage, calendar, tasks, pipeline)

2. Run each role as sub-agent with role-specific prompt

3. Aggregate responses

4. Synthesize into prioritized brief

5. Deliver via Telegram

Output Format

# 📋 Daily Brief — [Date]

## 🎯 Top 3 Priorities
1. [Most important thing]
2. [Second priority]
3. [Third priority]

## ⚠️ Risks & Blockers
- [Risk 1]
- [Blocker 1]

## 💡 Opportunities
- [Opportunity 1]

## 📊 Numbers
- Sessions: X | Cost: $Y | Trend: ↑/↓

## 🔄 Actions Recommended
- [ ] Action 1 (owner)
- [ ] Action 2 (owner)

Scheduled Runs

• **7:30am** — Morning brief (via existing cron)
• **6pm** — End of day summary (optional)
• **Sunday 8pm** — Weekly review (existing)

Configuration

Edit `references/council-config.json` to customize:

• Which roles to include
• Signal sources to check
• Output format
• Delivery channel