Cull Your Recurring Meetings

When to use it

The user's calendar is full of standing meetings, most of them inherited, and they want to know which to cut without upsetting anyone. One list in, one cut list out: a call per meeting, the arithmetic, and the note to send for each change. One sitting, done once; run it again when the calendar fills up.

Not for planning the week itself, or for deciding what to do with the hours recovered. The Weekly Planner pack does that. Not for one-off meetings: those are accepted or declined on their own merits.

What it asks you

Ask for everything in one numbered message.

1. Every recurring meeting on your calendar, one line each: name, length, how often, how many people attend, who runs it, and what it is for in your own words.
2. For each one: what was decided or assigned the last two times it ran. "Nothing" is a fine answer and the most useful one.
3. Which ones you run, and which ones you only attend.
4. Any meeting that cannot be touched: a client, a regulator, a board, a contract. Name them so they are kept without debate.
5. Optional: a loaded hourly cost per person, if you want the hours priced. If none, hours only.

Work from what comes back. If the user cannot say what a meeting is for, that is the finding, not a gap: mark it "no stated purpose". If the last-two-decisions answer is missing, mark it "not given" and do not score the meeting as if it had decided something. Never guess attendance, length or cost.

What comes back

Plain text. Headings in capitals.

CUT LIST One row per meeting: name, purpose word, last-two result, call with the rule number, hours a month before, hours a month after. Untouchable meetings and one-to-ones first, marked Keep.

ARITHMETIC Your hours a month: before, after, recovered. The sum behind every changed row. Team person-hours a month recovered, per changed meeting. Cost only if a rate was given.

NOTES One note per changed meeting, addressed to the attendees (meetings the user runs) or to the owner (meetings the user attends). Subject line, then under 80 words.

NOT DONE Meetings kept, with the reason, and any row where the user's answer was "not given".

Next: one line naming the single most useful next step.

• 00_START_HERE.pdf: the two-minute set-up for each AI.
• 1 - Skill: cull-recurring-meetings.zip, one upload to Claude, ChatGPT, Gemini, Grok or Microsoft 365 Copilot. It switches on by itself when this job comes up.
• 2 - Text file for any AI: the same Move as one .txt. Attach it to any chat, on any plan, and type "Follow this file".

It drafts, you read and send. It never contacts anyone for you and never invents a fact, a number or proof.

A Move is a single play. The whole function in a box is Weekly Planner, an agent pack with up to 8 skills.