Initial commit
This commit is contained in:
33
commands/design-event.md
Normal file
33
commands/design-event.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: design-event
|
||||
description: Generates an event brief with objectives, audience, agenda, experience design, and KPIs.
|
||||
usage: /event-marketing:design-event --type "executive dinner" --goal pipeline --region "US West"
|
||||
---
|
||||
|
||||
# Command: design-event
|
||||
|
||||
## Inputs
|
||||
- **type** – webinar, conference, dinner, field event, partner activation, etc.
|
||||
- **goal** – pipeline, expansion, community, product adoption, etc.
|
||||
- **region** – geography or segment.
|
||||
- **budget** – optional amount.
|
||||
- **timeline** – target month/date.
|
||||
|
||||
## Workflow
|
||||
1. **Objective Mapping** – align event purpose with KPIs and attendee personas.
|
||||
2. **Experience Blueprint** – recommend agenda, format, speakers, demos, activations.
|
||||
3. **Content & Offer Plan** – define narratives, assets, giveaways, CTAs.
|
||||
4. **Promotion Strategy** – outline invite journey, partner amplification, paid/organic mix.
|
||||
5. **Measurement Plan** – specify registration targets, attendance, engagement SLAs, post-event routing.
|
||||
|
||||
## Outputs
|
||||
- Event brief (objectives, agenda, deliverables, KPIs).
|
||||
- Creative/messaging checklist.
|
||||
- Promotion + follow-up plan outline.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `event-strategist` – leads strategy + alignment.
|
||||
- `event-briefs` skill – provides standardized template + guardrails.
|
||||
- `field-program-manager` – adds localization guidance if region-specific.
|
||||
|
||||
---
|
||||
33
commands/follow-up-impact.md
Normal file
33
commands/follow-up-impact.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: follow-up-impact
|
||||
description: Builds post-event follow-up plan plus impact report framework.
|
||||
usage: /event-marketing:follow-up-impact --event "Summit" --window 30d --kpis "pipeline,expansion"
|
||||
---
|
||||
|
||||
# Command: follow-up-impact
|
||||
|
||||
## Inputs
|
||||
- **event** – event identifier.
|
||||
- **window** – measurement horizon (7d/30d/quarter).
|
||||
- **kpis** – comma-separated metrics (pipeline, bookings, success metrics, NPS, meetings).
|
||||
- **segments** – optional segmentation (persona, region, tier).
|
||||
- **playbooks** – optional reference to follow-up sequences.
|
||||
|
||||
## Workflow
|
||||
1. **Attendee Data Prep** – consolidate registrations, attendance, engagement, notes.
|
||||
2. **Routing & Follow-up** – recommend SDR/CS outreach tiers, nurture sequences, partner touchpoints.
|
||||
3. **Measurement Framework** – map KPIs to data sources, dashboards, attribution rules.
|
||||
4. **Insight Summary** – capture qualitative feedback, booth conversations, survey highlights.
|
||||
5. **Retro Plan** – schedule retro, assign action items, document learnings.
|
||||
|
||||
## Outputs
|
||||
- Follow-up matrix (segment → owner → action → deadline).
|
||||
- KPI dashboard spec + SQL/Looker queries.
|
||||
- Retro template pre-filled with event context.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `field-program-manager` – coordinates regional follow-up.
|
||||
- `program-ops` skill – enforces routing/automation standards.
|
||||
- `field-playbooks` skill – suggests nurture/cadence templates.
|
||||
|
||||
---
|
||||
33
commands/manage-production.md
Normal file
33
commands/manage-production.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: manage-production
|
||||
description: Produces production plan with vendor checklist, run-of-show, and contingency matrix.
|
||||
usage: /event-marketing:manage-production --event "Summit" --format hybrid --attendees 500
|
||||
---
|
||||
|
||||
# Command: manage-production
|
||||
|
||||
## Inputs
|
||||
- **event** – name or identifier.
|
||||
- **format** – virtual, in-person, hybrid.
|
||||
- **attendees** – expected size.
|
||||
- **location** – optional venue/city/platform.
|
||||
- **vendors** – optional known vendors to include.
|
||||
|
||||
## Workflow
|
||||
1. **Requirements Intake** – gather AV, staging, streaming, accessibility, branding needs.
|
||||
2. **Vendor Plan** – suggest vendor categories, RFP questions, contract reminders.
|
||||
3. **Run-of-Show** – build detailed schedule with cues, speakers, technical notes.
|
||||
4. **Operational Checklist** – staffing, registration, signage, swag, catering, shipments.
|
||||
5. **Risk & Contingency** – highlight failure points (tech, weather, travel) with backup plans.
|
||||
|
||||
## Outputs
|
||||
- Production plan doc with responsibilities + deadlines.
|
||||
- Run-of-show table and cue sheets.
|
||||
- Risk matrix and escalation contacts.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `event-producer` – owns production plan.
|
||||
- `program-ops` skill – enforces ops standards.
|
||||
- `event-briefs` skill – ensures documentation completeness.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user