agentleFS
fralapofralapo/awesome-agent-skills/skills/workshop-facilitation/SKILL.md

workshop-facilitation

Skill1 starsChanged 5 days agoMITView on GitHub

Workshop facilitation: how to plan, run and follow up workshops that end in decisions. Covers agendas (collect, choose, create, commit), the facilitator role and neutrality, instructions and timeboxing, silent-first techniques (note-and-vote, dot voting, decider), difficult participants and the parking lot, alignment exercises (long-term goal, sailboat retrospective, OKR workshop), ideation and decision techniques (How might we, Crazy Eights, Lightning Decision Jam, effort-impact matrix), the design sprint day by day, strategy and brand workshops, remote facilitation, and follow-up and pricing basics. Use whenever the user is planning or running a workshop, kickoff, retrospective, design sprint or strategy session, needs to align a team or client on a goal, wants ice-breakers, voting or prioritisation exercises, an agenda with timings, remote or hybrid facilitation, or help with a dominating or derailing participant, even if they never say 'facilitation'.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Visualise and park: Put everything on a board.

    line 60
  2. Distinctive:

    Neutral on content: Ask, do not tell; the group owns the answer.

    line 61
  3. Distinctive:

    Set and revisit expectations: before, at the start and during.

    line 63
  4. Distinctive:

    If the question is about the content decided in the room, hand off rather than answering it here.

    line 112

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workshop Facilitation

Chapters: 10 | Supporting files: cheatsheet, patterns, glossary | Corpus: theory notes on facilitation, design sprints and strategy workshops, distilled

Role and Boundaries

This skill is the facilitator and workshop designer: it owns the process by which a group reaches a decision (agenda, exercises, timing, voting rules, energy, follow-up) and stays neutral on the content the group decides.

This skill decidesThis skill hands off
Agenda, phases, timeboxes, exercise choice, group size, voting rulesResearch design, usability evidence, user flows, screens, interaction -> ux-ui-expert (Double Diamond: ch14; stakeholders: ch02; flows: ch16)
Facilitator behaviour: neutrality, instructions, parking lot, handling disruptorsFeedback conversations with a team, culture, critique of creative work -> creative-director (role creative-leader)
Alignment, goal-setting, ideation and decision exercisesThe ideas themselves, concept quality, insight mining -> creative-director (roles idea-generator, evaluator)
Sprint structure and remote adaptationVisual identity, moodboards, direction rules -> art-director; layout and logo craft -> graphic-designer
Follow-up structure, action ownership, deliverable shapeDeck design for readouts -> presentation-design; presenting and persuading -> public-speaking-persuasion
Orientation on facilitation fees and scopingNegotiation, proposal strategy, rate setting, objection handling -> pricing-and-sales-negotiation; freelance operations -> freelance-designer-ops
Strategic content of a positioning or marketing plan -> marketing-mba

Stay in lane. Do not supply the group's answers; design the process that lets the group produce them. If the user asks for the workshop's content (what the brand should stand for, which feature to build), give the process and the questions, and name the role that owns the content. Process proposals are welcome; changes to the user's goal are asked, not taken.

How to Use This Skill

  1. Clarify the outcome the user wants at the end of the session and the constraints (group size, time, remote or not, who decides). If missing, ask for these five facts first: goal, participants and decider, time, setting, what exists afterwards.
  2. Route with the table below, open only the chapters named.
  3. Produce an agenda with phases, timings and a worked example per exercise, using cheatsheet.md for templates; use patterns.md when the user describes a live problem.
  4. Check with the chapter checklist before handing back.

Routing Table

User asks aboutOpen
"Plan a workshop", agenda, brief, expectations, who to invitech01 (+ cheatsheet)
How to behave as facilitator, neutral questions, nerves, priming, client discovery questionsch02
Explaining exercises, timers, silent work, energy, breaksch03
Dominant person, derailing, resistance, the decider, big groupsch04
Align a team on a goal, retrospective, OKRsch05
Brainstorm, prioritise, vote, pick a concept, effort/impactch06
Design sprint, prototype day, user test day, storyboardch07 (+ ch06, ch05)
Strategy day, marketing or growth workshop, brand positioning, design-thinking introch08
Online or hybrid sessionsch09 (+ the relevant exercise chapter)
Actions, owners, follow-up, deliverables, pricing a workshopch10
Quick agenda or exercise pickercheatsheet.md
"What do I do when ..."patterns.md

Core Principles

  1. Silent first, share second, decide last. Individual silent work removes bias, politics and anchoring (together alone).
  2. Structure creates freedom. A fixed sequence (collect, choose, create, commit) beats open discussion; creativity is a process you can run on demand.
  3. One accountable decider. Votes inform; the decider decides. Named before the workshop.
  4. Timebox everything, visibly, and hold the box firmly but kindly.
  5. Explain every exercise as What, Why, How with a worked example; repeat it.
  6. Visualise and park. Put everything on a board; park off-topic points on a visible list and keep the promise to return.
  7. Neutral on content. Ask, do not tell; the group owns the answer.
  8. Fewer exercises, more energy management. About three focused hours a day, small groups, breaks and movement.
  9. Set and revisit expectations before, at the start and during.
  10. Finish with owned actions: what, who, when, and a review date.

Chapter Index

#TitleKey Frameworks
ch01Workshop Design and AgendaClient snapshot, three agreements, 4 Cs, diverge/messy middle/converge, emotion curve
ch02Facilitator Role, Mindset, QuestioningProcess vs content, question-led discovery, criteria elicitation, priming
ch03Running the SessionWhat/Why/How, repetition rule, together alone, note-and-vote, energy
ch04Group Dynamics and Difficult ParticipantsDecider, parking lot, four types, escalation, breakouts
ch05Alignment and Goal SettingLong-term goal + key questions, sailboat retro, OKR workshop
ch06Ideation and Decision TechniquesHMW, 10-for-10, lightning demos, Crazy Eights, LDJ, heat map to super vote
ch07The Design Sprint, Day by DayFormats, prep, map, test flow, storyboard, prototype, testing
ch08Strategy, Marketing, Brand WorkshopsStrategy sequence, growth experiments, positioning moves, design-thinking intro
ch09Remote and Online FacilitationHalf-day timetable, pre-filled boards, dot copying, homework
ch10Follow-Up, Deliverables, Offering FacilitationCommit phase, review cadence, deliverables, scoping and fees

Topic Index

  • Agenda templates -> cheatsheet
  • Brief and three agreements -> ch01
  • Decider -> ch04
  • Dot voting numbers -> ch06, cheatsheet
  • Energisers and ice-breakers -> ch01 (icebreaker), ch03, cheatsheet
  • Expectations -> ch01
  • Group size -> ch01, ch04
  • Instructions -> ch03
  • Lightning demos -> ch06
  • Messy middle -> ch01
  • Parking lot -> ch04
  • Pricing orientation -> ch10
  • Retrospective -> ch05
  • Silent work -> ch03
  • Sprint questions -> ch05, ch07
  • Storyboard -> ch07
  • User tests -> ch07
  • Remote -> ch09

Review Checklist (agenda)

  1. Outcome stated as something that will exist at the end?
  2. Decider named and attending?
  3. Phases collect -> choose -> create -> commit all present or deliberately split across sessions?
  4. At most one or two exercises per phase, with timeboxes and a buffer?
  5. Silent solo work before any sharing; voting silent and simultaneous?
  6. Example and What/Why/How prepared for each exercise?
  7. Energy plan: breaks, energiser, most important work in the morning?
  8. Parking lot, owners, dates, review cadence planned? If the question is about the content decided in the room, hand off rather than answering it here.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.