workshop-facilitation
Skill62 starsChanged 11 days agoMITView on GitHub
Design and facilitate consulting workshops, strategy offsites, discovery sessions, prioritization, and design sprints. Use for agendas, participant activities, facilitation guides, pre-work, and follow-through for in-person, virtual, or hybrid groups.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- fralapo/awesome-agent-skillstheir own version, first seen Nov 8, 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
- henrique-simoes/Istara★ 15same name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- The-Utopia-Studio/skills★ 6same name
- agrivisionai/claude-skills★ 1same name
- fralapo/awesome-agent-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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-managementSkill
- client-deliverablesSkill
- due-diligenceSkill
- engagement-pricingSkill
- engagement-setupSkill
- financial-modelingSkill
- implementation-planningSkill
- org-designSkill
- process-excellenceSkill
- project-closeoutSkill
- project-governanceSkill
- proposal-developmentSkill
- strategic-analysisSkill
- thought-leadershipSkill
- writing-styleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
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 15
Use the known context and produce a useful agenda or guide with labeled assumptions.
- Distinctive: line 35
If pre-work cannot happen, build the necessary context into the session and reduce the ambition accordingly.
“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
Design a session that produces the learning, alignment, decision, or work product the user needs. Start with the objective, participants, authority, time available, format, and constraints. Discovery and learning are valid outcomes even when the group is not ready to choose a strategy.
Use the known context and produce a useful agenda or guide with labeled assumptions. Ask only when an unknown materially changes the design. Do not invent participant names, tensions, pre-work completion, decisions, or agreement. Respect the requested duration, accessibility needs, and participation preferences.
Design backward from the output
Specify what the group should produce and how it will be used. Identify the evidence, perspectives, and authority required. Separate generating ideas, evaluating them, recommending a choice, and making an authorized decision. A preference vote does not replace the decision-maker or override a hard constraint.
Select the activities needed for this outcome using formats and facilitation. Adapt methods and durations; an offsite need not take a full day, and an innovation session does not require a warmup when time or context argues against it.
For each activity, give its purpose, input, method, output, timing, and facilitator response to likely failure. Keep time labels compact and put facilitation detail in notes when an executive agenda should be short.
Make participation usable
Use silent reflection, written input, structured rounds, or anonymous ranking where hierarchy or speaking style could distort the evidence. Brief senior leaders on when their input is needed without treating their silence as a universal requirement. Let participants contribute through accessible alternatives; camera use is a preference or local policy, not a condition of meaningful participation.
For hybrid sessions, provide a shared digital or otherwise equally accessible workspace, explicit remote turns, and a way to contribute when audio or a tool fails. Do not move to an in-room-only activity while remote participants lose access. If decision-critical participants cannot participate, use an agreed delegate, mark the result provisional, or reschedule the decision.
Check time and dependencies
Calculate the agenda from start to finish, including transitions, breaks, synthesis, and close. Choose sustained work intervals and breaks to fit the audience, activity, access needs, and available time. Do not ship a template that contradicts its stated break pattern.
If pre-work cannot happen, build the necessary context into the session and reduce the ambition accordingly. Plan what to cut if discussion runs long. Preserve the closing record and the authority needed for any decision rather than rushing untested consensus.
Close and follow through
Record outputs, decisions, dissent or unresolved questions, decision authority, and actions with owners and timing. Distinguish workshop recommendations from approved commitments. If the task is planning, produce a plan for capturing these results; do not fabricate a post-session summary.
Deliver the agenda, facilitator guide, activity materials, or summary requested. Verify timing, input availability, participant access, and the decision mechanism. Propose follow-up proportional to the work. Sending invitations, distributing materials, recording participants, or scheduling follow-ups requires the user's authorization; drafting them does not.
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.

