Skip to main content

define-an-event-brief

Turn an event idea into a bounded brief with outcomes, audience, constraints, and evidence. Use when organizers need an agreed basis for planning before choosing format, venue, or suppliers.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
define-an-event-brief
category
write
description
Turn an event idea into a bounded brief with outcomes, audience, constraints, and evidence. Use when organizers need an agreed basis for planning before choosing format, venue, or suppliers.
# define-an-event-brief ## Procedure 1. Name the sponsor, decision owner, intended audience, problem, and desired change. 2. Define measurable outcomes and distinguish them from attendance, activity, or publicity. 3. Record scope, format options, timing, location, budget range, capacity, and delivery constraints. 4. Include accessibility, safety, safeguarding, privacy, sustainability, and inclusion needs. 5. Identify stakeholders, dependencies, assumptions, exclusions, and unresolved decisions. 6. Compare in-person, virtual, hybrid, series, and no-event alternatives. 7. Define success evidence, review points, approval authority, and change control. 8. Obtain sponsor and delivery-owner agreement before detailed commitments. ## Guardrails - Do not invent audience demand or promise outcomes without evidence. - Never commit venue, speakers, suppliers, or public dates without authority. - Keep personal, commercial, and security-sensitive assumptions within the approved audience. ## Done - An event brief records audience, outcomes, scope, constraints, options, and owners - Success measures, assumptions, exclusions, and approval evidence are explicit - Sponsor and delivery-owner acceptance is recorded
View on GitHub