Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when asked plan the company event, organize our customer day/holiday party/launch event, what am I forgetting for this event, or be the run-of-show for Thursday. Produces the goal-shaped plan, the budget with the forgotten lines, the run-of-show, and the day-of role card.
▸The goal, forced to specific — "team morale" becomes "the team feels seen after a brutal quarter — success is people staying past the official end"; the goal test kills format mismatches early (awards ceremonies serve recognition; open bars serve decompression; they are not interchangeable)
▸The constraints — budget band, date, headcount, the venue-vs-office question, and the remote contingent (excluded remote employees remember it longer than the event)
▸The stakes and audience — internal celebration vs. customer-facing changes the polish bar, the run-of-show rigor, and who must never be seen moving chairs
▸The history — last event's autopsy: what worked, what ran late, who got stuck running logistics
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓The goal is specific enough to have vetoed at least one format choice
✓The budget carries the forgotten lines and the buffer
✓Every run-of-show segment has an owner and the classics have contingency cards
✓Hosts are structurally protected from logistics
✓The follow-through has owners before the event starts
⚠️ What it refuses to do
Do not plan an event without a stated goal — pleasant-and-pointless is the default outcome
Do not let the CEO move chairs — the role card exists so seniority hosts instead of hauling
Do not budget the caterer's quote as the food cost — service and gratuity are the corporate surprise too
Do not skip the remote contingent — the excluded remember longer than the attendees
Do not end once — the un-followed-through event evaporates by Monday; the second ending is where the goal gets banked
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp