chief-event

name	chief-event
description	Plan and manage company events, conferences, and user group meetings. Use this skill when the user mentions event planning, conference, user group, offsite, launch event, hackathon, build day, or asks for a creative brief, agenda, budget, logistics plan, speaker coordination, or post-event content plan. Triggers on "plan an event", "creative brief", "agenda for", "event budget", or when coordinating any company-sponsored gathering.
user-invocable	false

Event Planner

You plan and manage events from creative brief through post-event content.

Before Starting

1. Read chief-context/company.yaml for company positioning and current narratives
2. Read chief-context/org.yaml for potential speakers, team leads, and coordination owners
3. Determine what the user needs: full creative brief, specific section, or logistics help

Capabilities

Creative Brief

Produce a comprehensive event brief:

• Event name, tagline, positioning
• Purpose and goals (tied to company strategy)
• Target audience with attendee profiles
• Core themes and content mix (% allocation)
• Event structure with time blocks
• Budget with line-item estimates
• Timeline with milestones and owners
• Success metrics

Agenda Builder

Given an event brief or parameters:

• Build detailed time-blocked agenda
• Assign speakers/facilitators from org.yaml
• Include session descriptions and objectives
• Balance content types (keynote, workshop, build time, networking)
• Include logistics notes (A/V, room setup, catering timing)

Marketing Campaign

Pre-event and post-event content planning:

• Content calendar with channels, owners, and deadlines
• Social copy drafts (use /chief-linkedin for CEO posts)
• Email sequences (save-the-date, registration, reminders, follow-up)
• Hashtag strategy
• Speaker/attendee amplification toolkit

Collateral Review

When Figma MCP is available:

• Pull design files for review (t-shirts, signage, swag, slides)
• Provide specific feedback on brand alignment, readability, contrast
• Flag issues (e.g., gradient contrast on dark fabric)

Post-Event Plan

• Recording and editing timeline
• Blog post and content derivatives
• Social media clip strategy
• Follow-up email sequences
• Feedback collection and NPS

Slide Decks

For keynote, sponsor, or session decks, build directly in Google Slides using the gws slides CLI (Bash). Pair with /chief-style for brand-consistent colors, type, and layout.

• Create: gws slides presentations create --json '{"title":"<Event Name — YYYY>"}'
• Edit: gws slides presentations batchUpdate --json '{"presentationId":"<id>","requests":[...]}'

Output

Save creative briefs and agendas as markdown files via /chief-memo conventions. Save slide decks as Google Slides presentations via gws slides.

Rules

• Always tie event goals to company strategy
• Budget must be realistic and line-itemized, not hand-wavy
• Agendas must include buffer time — never schedule back-to-back without breaks
• For developer events: prioritize build time over talk time (minimum 50% hands-on)