agenda-or-cancel
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/agenda-or-cancel && cp -r /tmp/agenda-or-cancel/exports/openclaw/agenda-or-cancel ~/.claude/skills/agenda-or-cancelSKILL.md
# 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](../standing-meeting-audit/SKILL.md) for the deeper treatment ## Framework: The Test Rules 1. **The agenda is three lines or the meeting is fiction:** *Purpose:* why we're gathering, one sentence. *Outcomes:* the decisions or artifacts this meeting produces (verbs, not topics). *Pre-reads:* what to read and how long it takes. If line two can't list a decision or artifact, the meeting is a broadcast — and broadcasts are messages. 2. **The 24-hour rule:** agenda ships with (or ≥24h before) the invite — attendees who can't prepare attend as audience, and audiences don't decide. Meetings that can't produce an agenda a day out aren't urgent; they're unformed. 3. **The verdict follows the attempt:** agenda writes cleanly → happen (at the length the outcomes justify — most three-line agendas fit 25 minutes). Outcomes are all information-transfer → convert to a message/doc. Purpose exists but no decisions this week → shorten or skip this instance. Nothing survives writing down → cancel, with the script. 4. **Declining needs a cheap script:** "Happy to join — could you share the agenda first so I can prep?" does the enforcement politely; the norm survives only if asking is routine, not confrontational. Organizer-side cancel: "Cancelling — the two items resolved async / aren't ready for decisions yet. Reconvening when [trigger]." 5. **Roll out as a gift, not a law:** the team adopts "agenda-or-cancel" by the leader modeling it on their *own* meetings first (cancelling one publicly is worth ten policy emails), the three-line format pinned where invites happen, and the decline script blessed explicitly so juniors can use it upward. ## Output Format # Agenda Test: [meeting] ## The Three Lines **Purpose:** … **Outcomes:** [decisions/artifacts, verbs] **Pre-reads:** [links + minutes] ## The Verdict [Happen ([N] min) / shorten / convert / cancel — with the reasoning from the attempt] ## Scripts (as needed) [The cancel · the convert-to-message · the agenda-first decline] ## Rollout (for teams installing the norm) [Leader models on own meetings · format pinned · decline script blessed downward and upward] ## Quality Checks - [ ] The outcomes line contains decisions or artifacts, not topic nouns - [ ] Pre-reads carry their time cost - [ ] The verdict came from the writing attempt, not from meeting-hating priors - [ ] Every script is usable by the most junior attendee - [ ] Recurring meetings were routed to the audit instead of one-off verdicts ## Anti-Patterns - [ ] Do not write topic agendas — "discuss roadmap" is a location, not a purpose - [ ] Do not accept "we'll figure it out live" — that's the agenda test failing in real time, at full attendance - [ ] Do not use the rule as a weapon — the verdict includes "happen"; meeting-zero is not the goal, meeting-earned is - [ ] Do not ship the agenda at meeting-start — unprepped deciders are attendees - [ ] Do not install the norm by decree — the leader's own cancelled meeting is the announcement
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.