agenda-or-cancel
Agent skill frommohitagw15856/pm-claude-skills
Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line agenda format (purpose, decisions sought, pre-reads), the 24-hour rule, and the graceful cancel scripts. Use when asked write an agenda for this meeting, should this meeting happen, our meetings have no agendas, or cancel this meeting politely. Produces the three-line agenda, the happen-or-cancel verdict, the cancel/convert scripts, and the team norm rollout.
How to install agenda-or-cancel
install agenda-or-cancel
# install the pm-claude-skills pack with the skills CLI
npx skills add mohitagw15856/pm-claude-skills# or add only this skill to Claude Code: copy the folder
skills/agenda-or-cancel/
# into
~/.claude/skills/agenda-or-cancel/ (all projects)
.claude/skills/agenda-or-cancel/ (one project)
1# Agenda Or Cancel Skill23The 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.45## What This Skill Produces67- **The three-line agenda** — purpose (one sentence), decisions/outcomes sought (listed), pre-reads with time cost8- **The verdict** — happen / shorten / convert-to-async / cancel — from the agenda-writing attempt itself9- **The scripts** — the polite cancel, the convert-to-message, and the decline-without-agenda lines10- **The norm rollout** — how a team installs the rule without a compliance war1112## Required Inputs1314Ask for these if not provided:15- **The meeting's claimed purpose** — what the organizer thinks it's for; the agenda attempt tests whether that survives writing down16- **The attendee list and length** — the cost side (people × time), which the purpose must justify17- **What a good outcome looks like** — a decision? alignment? information moved? If the outcome is "information moved," the convert-to-async branch is already winning18…
Excerpt shown under the repository's MIT license.
