Menu

Individual skill

standing-meeting-audit

0upvotes

Audit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our calendar is all standing syncs, which meetings should die, or reset the team's meeting load. Produces the inventory with per-meeting verdicts, the experiment protocol, the merge map, and the re-accretion guard.

plugins/pm-cowork/skills/standing-meeting-audit/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Standing Meeting Audit Skill

Standing meetings are organizational scar tissue: each was created for a reason, the reason healed, the meeting remained. Nobody audits them because each is individually defensible-ish and collectively they're the calendar. The audit tests each slot against three questions — does the original purpose still exist, does the attendance reflect it, what has it produced lately — renders verdicts (keep / shrink / merge / kill / experiment), and deploys the un-arguable tool: *cancel it for two weeks and see what breaks.* Almost nothing breaks, and what breaks reveals the meeting's true minimal form.

## What This Skill Produces

- **The inventory** — every recurring meeting: origin purpose, current attendance, recent outcomes, annualized cost (via [meeting-cost-meter](../meeting-cost-meter/SKILL.md))
- **The verdicts** — keep / shrink (length, cast, or frequency) / merge / kill / two-week-experiment, with reasons
- **The experiment protocol** — how the pause runs, what "broke" means, and the decision rule at the end
- **The re-accretion guard** — expiry dates on new standing meetings, and the quarterly re-audit

## Required Inputs

Ask for these if not provided:
Back to top