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
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
- NinjaSln-labs/agent-skillstheir own version, first seen Oct 2, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- anotb/management-consulting-plugin★ 62same name
- henrique-simoes/Istara★ 15same name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- The-Utopia-Studio/skills★ 6same name
- agrivisionai/claude-skills★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- NinjaSln-labs/agent-skills★ 1same name
- Samueladewole/claude-skills★ 0same name
- vijaysuperpositionist/skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- art-directorSkill
- awesome-readmeSkill
- brand-strategy-storytellingSkill
- creative-directorSkill
- depth-psychologySkill
- designcraft-expertSkill
- effectcraft-expertSkill
- ffmpegSkill
- filmcraft-expertSkill
- freelance-designer-opsSkill
- geo-ai-visibilitySkill
- graphic-designerSkill
- image-gen-promptsSkill
- jevSkill
- llm-wikiSkill
- marketing-mbaSkill
- photocraft-expertSkill
- presentation-designSkill
- pricing-and-sales-negotiationSkill
- public-speaking-persuasionSkill
- seedance-promptsSkill
- slide-software-techniquesSkill
- social-algorithmSkill
- ux-ui-expertSkill
- vectorcraft-expertSkill
- video-editorSkill
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
- Distinctive: line 60
Visualise and park: Put everything on a board.
- Distinctive: line 61
Neutral on content: Ask, do not tell; the group owns the answer.
- Distinctive: line 63
Set and revisit expectations: before, at the start and during.
- Distinctive: line 112
If the question is about the content decided in the room, hand off rather than answering it here.
“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.
Files
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 decides | This skill hands off |
| Agenda, phases, timeboxes, exercise choice, group size, voting rules | Research design, usability evidence, user flows, screens, interaction -> ux-ui-expert (Double Diamond: ch14; stakeholders: ch02; flows: ch16) |
| Facilitator behaviour: neutrality, instructions, parking lot, handling disruptors | Feedback conversations with a team, culture, critique of creative work -> creative-director (role creative-leader) |
| Alignment, goal-setting, ideation and decision exercises | The ideas themselves, concept quality, insight mining -> creative-director (roles idea-generator, evaluator) |
| Sprint structure and remote adaptation | Visual identity, moodboards, direction rules -> art-director; layout and logo craft -> graphic-designer |
| Follow-up structure, action ownership, deliverable shape | Deck design for readouts -> presentation-design; presenting and persuading -> public-speaking-persuasion |
| Orientation on facilitation fees and scoping | Negotiation, 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
- 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.
- Route with the table below, open only the chapters named.
- 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.
- Check with the chapter checklist before handing back.
Routing Table
| User asks about | Open |
| "Plan a workshop", agenda, brief, expectations, who to invite | ch01 (+ cheatsheet) |
| How to behave as facilitator, neutral questions, nerves, priming, client discovery questions | ch02 |
| Explaining exercises, timers, silent work, energy, breaks | ch03 |
| Dominant person, derailing, resistance, the decider, big groups | ch04 |
| Align a team on a goal, retrospective, OKRs | ch05 |
| Brainstorm, prioritise, vote, pick a concept, effort/impact | ch06 |
| Design sprint, prototype day, user test day, storyboard | ch07 (+ ch06, ch05) |
| Strategy day, marketing or growth workshop, brand positioning, design-thinking intro | ch08 |
| Online or hybrid sessions | ch09 (+ the relevant exercise chapter) |
| Actions, owners, follow-up, deliverables, pricing a workshop | ch10 |
| Quick agenda or exercise picker | cheatsheet.md |
| "What do I do when ..." | patterns.md |
Core Principles
- Silent first, share second, decide last. Individual silent work removes bias, politics and anchoring (together alone).
- Structure creates freedom. A fixed sequence (collect, choose, create, commit) beats open discussion; creativity is a process you can run on demand.
- One accountable decider. Votes inform; the decider decides. Named before the workshop.
- Timebox everything, visibly, and hold the box firmly but kindly.
- Explain every exercise as What, Why, How with a worked example; repeat it.
- Visualise and park. Put everything on a board; park off-topic points on a visible list and keep the promise to return.
- Neutral on content. Ask, do not tell; the group owns the answer.
- Fewer exercises, more energy management. About three focused hours a day, small groups, breaks and movement.
- Set and revisit expectations before, at the start and during.
- Finish with owned actions: what, who, when, and a review date.
Chapter Index
| # | Title | Key Frameworks |
| ch01 | Workshop Design and Agenda | Client snapshot, three agreements, 4 Cs, diverge/messy middle/converge, emotion curve |
| ch02 | Facilitator Role, Mindset, Questioning | Process vs content, question-led discovery, criteria elicitation, priming |
| ch03 | Running the Session | What/Why/How, repetition rule, together alone, note-and-vote, energy |
| ch04 | Group Dynamics and Difficult Participants | Decider, parking lot, four types, escalation, breakouts |
| ch05 | Alignment and Goal Setting | Long-term goal + key questions, sailboat retro, OKR workshop |
| ch06 | Ideation and Decision Techniques | HMW, 10-for-10, lightning demos, Crazy Eights, LDJ, heat map to super vote |
| ch07 | The Design Sprint, Day by Day | Formats, prep, map, test flow, storyboard, prototype, testing |
| ch08 | Strategy, Marketing, Brand Workshops | Strategy sequence, growth experiments, positioning moves, design-thinking intro |
| ch09 | Remote and Online Facilitation | Half-day timetable, pre-filled boards, dot copying, homework |
| ch10 | Follow-Up, Deliverables, Offering Facilitation | Commit 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)
- Outcome stated as something that will exist at the end?
- Decider named and attending?
- Phases collect -> choose -> create -> commit all present or deliberately split across sessions?
- At most one or two exercises per phase, with timeboxes and a buffer?
- Silent solo work before any sharing; voting silent and simultaneous?
- Example and What/Why/How prepared for each exercise?
- Energy plan: breaks, energiser, most important work in the morning?
- 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.
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
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.

