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
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.