AGENT SKILL

board-meeting

Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.

License 许可
MIT
最近更新
2026-07-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
board-meeting
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "board-protocol", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "6-phase-board, two-layer-memory, independent-contributions" }
description
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.

02 资源文件 3

03 SKILL.md 正文

Board Meeting Protocol

Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.

Keywords

board meeting, executive deliberation, strategic decision, C-suite, multi-agent, /cs:boardroom, founder review, decision extraction, independent perspectives

Invoke

/cs:boardroom [topic] — e.g. /cs:boardroom Should we expand to Spain in Q3?


The 6-Phase Protocol

PHASE 1: Context Gathering

  1. Load ~/.claude/company-context.md
  2. Load Layer 2 approved decisions from ~/.claude/decisions/approved/ (Layer 2 ONLY — never raw transcripts)
  3. Reset session state — no bleed from previous conversations
  4. Present agenda + activated roles → wait for founder confirmation

Chief of Staff selects relevant roles based on topic (not all 14 every time):

Topic Activate
Market expansion CEO, CMO, CFO, CRO, COO
Product direction CEO, CPO, CTO, CMO
Hiring/org CEO, CHRO, CFO, COO (+ VPE for eng hiring)
Pricing CMO, CFO, CRO, CPO
Technology CTO, CPO, CFO, CISO
Contracts / term sheets / legal exposure GC, CEO, CFO
Data strategy / training-data rights CDO, CAIO, GC, CISO
AI strategy / model selection / AI risk CAIO, CTO, CDO, CFO
Retention / churn / customer success CCO, CRO, CPO
Eng delivery / DORA / team structure VPE, CTO, CHRO, CFO

PHASE 2: Independent Contributions (ISOLATED)

No cross-pollination. Each agent runs before seeing others' outputs.

Order: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO → GC → CDO → CAIO → CCO → VPE (activated roles only)

Reasoning techniques: CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)

Contribution format (max 5 key points, self-verified):

## [ROLE] — [DATE]

Key points (max 5):
• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴
• [Finding] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴

Recommendation: [clear position]
Confidence: High / Medium / Low
Source: [where the data came from]
What would change my mind: [specific condition]

Each agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.


PHASE 3: Critic Analysis

Executive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.

Checklist:

  • Where did agents agree too easily? (suspicious consensus = red flag)
  • What assumptions are shared but unvalidated?
  • Who is missing from the room? (customer voice? front-line ops?)
  • What risk has nobody mentioned?
  • Which agent operated outside their domain?

PHASE 4: Synthesis

Chief of Staff delivers using the Board Meeting Output format (defined in ../agent-protocol/SKILL.md):

  • Decision Required (one sentence)
  • Perspectives (one line per contributing role)
  • Where They Agree / Where They Disagree
  • Critic's View (the uncomfortable truth)
  • Recommended Decision + Action Items (owners, deadlines)
  • Your Call (options if founder disagrees)

PHASE 5: Human in the Loop ⏸️

Full stop. Wait for the founder.

⏸️ FOUNDER REVIEW — [Paste synthesis]

Options: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up

Rules:

  • User corrections OVERRIDE agent proposals. No pushback. No "but the CFO said..."
  • 30-min inactivity → auto-close as "pending review"
  • Reopen any time with /cs:boardroom resume

PHASE 6: Decision Extraction

After founder approval:

  • Layer 1: Write full transcript → ~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md
  • Layer 2: Write approved decision record → ~/.claude/decisions/approved/YYYY-MM-DD-<slug>.md and append to the index ~/.claude/decisions/approved/decisions.md
  • Mark rejected proposals [DO_NOT_RESURFACE]
  • Confirm to founder with count of decisions logged, actions tracked, flags added

Memory Structure

Uses the canonical two-layer decision memory (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)"):

~/.claude/decisions/
├── raw/YYYY-MM-DD-<slug>.md        # Layer 1 — full transcripts (never auto-loaded)
├── raw/archive/YYYY/               # Raw transcripts after 90 days
├── approved/YYYY-MM-DD-<slug>.md   # Layer 2 — founder-approved records (Phase 1 loads these)
└── approved/decisions.md           # Layer 2 index — append-only

Future meetings load Layer 2 only. Never Layer 1. This prevents hallucinated consensus.

Migration: a legacy memory/board-meetings/ folder may exist from earlier versions; read it for history but write new transcripts and decisions to ~/.claude/decisions/.


Failure Mode Quick Reference

Failure Fix
Groupthink (all agree) Re-run Phase 2 isolated; force "strongest argument against"
Analysis paralysis Cap at 5 points; force recommendation even with Low confidence
Bikeshedding Log as async action item; return to main agenda
Role bleed (CFO making product calls) Critic flags; exclude from synthesis
Layer contamination Phase 1 loads ~/.claude/decisions/approved/ only — hard rule

References

  • templates/meeting-agenda.md — agenda format
  • templates/meeting-minutes.md — final output format
  • references/meeting-facilitation.md — conflict handling, timing, failure modes

04 同仓库更多 Skills

sat-yam09
sat-yam09/omni-skill

youtube-full

Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.

★ 0
sat-yam09
sat-yam09/omni-skill

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 0
sat-yam09
sat-yam09/omni-skill

webinar-marketing

When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).

★ 0
sat-yam09
sat-yam09/omni-skill

vpe-advisor

VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.

★ 0
sat-yam09
sat-yam09/omni-skill

vendor-management

Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on "vendor SLA", "vendor scorecard", "third-party risk", "TPRM", "vendor review", "supplier performance", "vendor health check", "renewal review".

★ 0
sat-yam09
sat-yam09/omni-skill

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.

★ 0