Agenda Or Cancel Skill

The agenda isn't paperwork — it's the meeting's existence test. A meeting whose organizer can't write three lines (what this is for, what we'll decide, what to read first) is a meeting that hasn't earned its attendee-hours, and the kindest outcome is its cancellation or conversion to a message. This skill writes the agenda when one can be written, renders the cancel verdict when it can't, and scripts the graceful exits — because "no agenda, no meeting" only works as a norm when declining is socially cheap.

What This Skill Produces

• The three-line agenda — purpose (one sentence), decisions/outcomes sought (listed), pre-reads with time cost
• The verdict — happen / shorten / convert-to-async / cancel — from the agenda-writing attempt itself
• The scripts — the polite cancel, the convert-to-message, and the decline-without-agenda lines
• The norm rollout — how a team installs the rule without a compliance war

Required Inputs

Ask for these if not provided:

• The meeting's claimed purpose — what the organizer thinks it's for; the agenda attempt tests whether that survives writing down
• The attendee list and length — the cost side (people × time), which the purpose must justify
• What a good outcome looks like — a decision? alignment? information moved? If the outcome is "information moved," the convert-to-async branch is already winning
• The recurring-or-oneoff status — recurring meetings route to standing-meeting-audit for the deeper treatment