skills/facilitation-patterns/SKILL.md
Provides structured formats and techniques for running productive group sessions, from standups to multi-day workshops. Covers format selection, agenda design, participation management, decision methods, and handling difficult dynamics. Use when running meetings, workshops, brainstorms, design sprints, retrospectives, or team decision-making sessions, or when user mentions facilitation, workshop design, meeting patterns, session planning, or effective collaboration.
npx skillsauth add lyndonkl/claude facilitation-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scenario: Product team needs to prioritize features for Q2 (8 people, 90 minutes).
Pattern: Effort-Impact Workshop (diverge, assess, converge)
Agenda:
Copy this checklist and track your progress:
Facilitation Planning Progress:
- [ ] Step 1: Define session objectives
- [ ] Step 2: Select facilitation pattern
- [ ] Step 3: Design agenda
- [ ] Step 4: Prepare materials and logistics
- [ ] Step 5: Facilitate the session
- [ ] Step 6: Close and follow up
Step 1: Define session objectives
What outcome do you need? (Decision, ideas, alignment, learning, relationship-building). Who attends? How much time? See resources/template.md.
Step 2: Select facilitation pattern
Based on objective and group size, choose pattern (Brainstorm, Decision Workshop, Alignment Session, Retro, Design Sprint). See Common Patterns and resources/methodology.md.
Step 3: Design agenda
Create time-boxed agenda with activities, transitions, breaks. Follow diverge-converge flow. See resources/template.md and resources/methodology.md.
Step 4: Prepare materials and logistics
Set up space (physical or virtual), prepare slides/boards, send pre-work if needed, test tech. See resources/template.md.
Step 5: Facilitate the session
Run agenda, manage time, ensure participation, handle dynamics, track outputs. See resources/methodology.md and resources/methodology.md.
Step 6: Close and follow up
Summarize outcomes, clarify next steps and owners, gather feedback, share notes. See resources/template.md.
Validate using resources/evaluators/rubric_facilitation_patterns.json. Minimum standard: Average score ≥ 3.5.
Pattern 1: Divergent Brainstorm (Generate Ideas)
Pattern 2: Convergent Decision Workshop (Choose Direction)
Pattern 3: Alignment Session (Build Shared Understanding)
Pattern 4: Retrospective (Reflect and Improve)
Pattern 5: Design Sprint (Prototype and Test)
Pattern 6: Asynchronous Collaboration (Remote/Distributed)
Objectives before format: Start with "what outcome do we need?" not "let's do a brainstorm." If the objective is unclear, the session will drift.
Time-box activities: Parkinson's Law means work expands to fill time. Set strict timers, end activities even if incomplete. 25 minutes of focused work beats open-ended discussion.
Separate divergence from convergence: Defer judgment during brainstorming, because critiquing ideas early kills creativity. Generate first, evaluate second.
Ensure psychological safety: Set ground rules (no interrupting, critique ideas not people). Address power dynamics (boss speaks last, use anonymous input). Without safety, the result is groupthink or silence.
Manage participation actively: Use individual writing, round robin, and small groups to draw out quieter participants. Use time limits and parking lots to manage those who dominate.
Decide how decisions are made: Consensus, consent, majority vote, or delegation. Announce the method upfront to avoid "I thought we decided, but nothing happened."
Track outputs visibly: Shared board, live doc, or sticky notes so everyone sees the same thing. Assign a scribe. Invisible outputs are easily lost.
Close with clarity: State what was decided, who does what by when, what is still open, and how the group will communicate.
Common pitfalls:
Key resources:
Decision-making methods:
Participation techniques:
Energizers (5-10 min):
Timing guidelines:
Red flags (adjust or stop session):
50% on laptops/phones (not engaged) → take break, energizer, or change format
Inputs required:
Outputs produced:
facilitation-plan.md: Session design (objective, agenda, materials, decision method, outputs)session-notes.md: What was discussed, decisions made, action items with ownerstesting
--- name: advisory-edit description: A strict advisory-only editing discipline for a writer who dictates ("speaks out") essays and wants help WITHOUT having their voice changed. The editor directs structure, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply" / "make that change" / "rewrite this." Produces a line-referenced, suggestion-only critique where every item is marked the writer's call. Four passes: structural, l
testing
Provides the house style for analyst-grade strategist writing — third-person register with sparing first-person, no em dashes, no "not X, not Y, not Z" negation cascades, numbered footnote citations rather than inline source parentheticals, specific opinion-signaling phrases, and topic-forward paragraph structure modeled on voice patterns observed in Damodaran's Musings on Markets and Thompson's Stratechery. Use when consolidating working notes into a finished long-form strategist or analyst report that must read as written by a senior human analyst rather than an AI assistant.
testing
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
testing
Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introducing an operation that's intimidating in symbol form but trivial in pencil-and-paper form.