agentleFS
anotbanotb/management-consulting-plugin/skills/workshop-facilitation/SKILL.md

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

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
  1. Distinctive:

    Use the known context and produce a useful agenda or guide with labeled assumptions.

    line 15
  2. Distinctive:

    If pre-work cannot happen, build the necessary context into the session and reduce the ambition accordingly.

    line 35

“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

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.

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.