Meeting Design

Designs a meeting before it happens so it produces a decision rather than a discussion that has to be repeated. Trigger whenever the user says "plan this meeting", "build an agenda", "agenda for", "run a workshop", "facilitate", "offsite", "kickoff", "planning session", "how should I structure this meeting", "who should be in this meeting", "this meeting keeps going in circles", or names an upcoming meeting and asks what to do with it. Also trigger when they ask whether the meeting is needed at all, or when a recurring meeting has stopped producing anything. It names the decision, picks the decision rule out loud, sizes the room, sequences divergence before convergence, and plans for deadlock before it happens. Ships fill-in agenda templates rather than advice. Use a call-recap or meeting-notes skill for what happens after the meeting; this one is for before.

mkdir -p ~/.claude/skills/meeting-design
curl -L https://claudskills.com/skills/meeting-design/SKILL.md \
  -o ~/.claude/skills/meeting-design/SKILL.md

@misc{meeting-design-2026,
  author    = {ClaudSkills},
  title     = {Meeting Design [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/meeting-design/}
}