facilitation-patterns
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.
What this skill does
# Facilitation Patterns ## Table of Contents - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Example **Scenario**: Product team needs to prioritize features for Q2 (8 people, 90 minutes). **Pattern**: Effort-Impact Workshop (diverge, assess, converge) **Agenda**: 1. **Frame** (10 min): Present context, Q2 goals, constraints 2. **Diverge** (20 min): Silent brainstorm on sticky notes 3. **Cluster** (15 min): Group similar ideas, clarify duplicates 4. **Assess** (25 min): Plot on effort-impact 2x2 matrix (in pairs, then discuss) 5. **Converge** (15 min): Dot voting on quick wins 6. **Decide** (10 min): Top 5 by votes, facilitator makes final call with input 7. **Close** (5 min): Summarize decisions, next steps ## Workflow 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](resources/template.md#session-design-template). **Step 2: Select facilitation pattern** Based on objective and group size, choose pattern (Brainstorm, Decision Workshop, Alignment Session, Retro, Design Sprint). See [Common Patterns](#common-patterns) and [resources/methodology.md](resources/methodology.md#1-pattern-selection-guide). **Step 3: Design agenda** Create time-boxed agenda with activities, transitions, breaks. Follow diverge-converge flow. See [resources/template.md](resources/template.md#agenda-design-template) and [resources/methodology.md](resources/methodology.md#2-agenda-design-principles). **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](resources/template.md#logistics-checklist). **Step 5: Facilitate the session** Run agenda, manage time, ensure participation, handle dynamics, track outputs. See [resources/methodology.md](resources/methodology.md#3-facilitation-techniques) and [resources/methodology.md](resources/methodology.md#4-handling-difficult-dynamics). **Step 6: Close and follow up** Summarize outcomes, clarify next steps and owners, gather feedback, share notes. See [resources/template.md](resources/template.md#closing-and-followup-template). Validate using [resources/evaluators/rubric_facilitation_patterns.json](resources/evaluators/rubric_facilitation_patterns.json). **Minimum standard**: Average score ≥ 3.5. ## Common Patterns **Pattern 1: Divergent Brainstorm (Generate Ideas)** - **Goal**: Maximum idea generation, creative exploration - **Format**: Silent individual brainstorm → share → cluster → refine - **Techniques**: Crazy 8s, SCAMPER, "Yes, and...", defer judgment - **Time**: 30-60 min for 5-10 people - **Output**: 30-100 ideas, clustered by theme - **When**: Need creative options, early in project, no single right answer **Pattern 2: Convergent Decision Workshop (Choose Direction)** - **Goal**: Narrow options, make decision with group input - **Format**: Present options → assess criteria → vote/rank → decide - **Techniques**: 2×2 matrix (effort-impact), dot voting, affinity grouping, forced ranking - **Time**: 60-90 min for decision, 2-3 hours for complex - **Output**: Prioritized list or single decision with rationale - **When**: Multiple options exist, need buy-in, criteria clear **Pattern 3: Alignment Session (Build Shared Understanding)** - **Goal**: Get everyone on same page (vision, strategy, plan) - **Format**: Present → Q&A → small group discussion → report back → synthesize - **Techniques**: Fishbowl, gallery walk, 1-2-4-All, consensus check - **Time**: 90-120 min for alignment, half-day for strategy - **Output**: Shared mental model, documented assumptions, commitments - **When**: Starting project, misalignment detected, new team formation **Pattern 4: Retrospective (Reflect and Improve)** - **Goal**: Learn from experience, identify improvements - **Format**: Set context → gather data → generate insights → decide actions → close - **Techniques**: Start-Stop-Continue, Mad-Sad-Glad, Timeline, Sailboat, 4Ls (Liked, Learned, Lacked, Longed for) - **Time**: 45-90 min for sprint retro, 2-3 hours for project postmortem - **Output**: 2-5 actionable improvements with owners - **When**: End of sprint/project, recurring team practice, after incident **Pattern 5: Design Sprint (Prototype and Test)** - **Goal**: Rapidly prototype and validate concept - **Format**: 5 days: Understand → Diverge → Decide → Prototype → Test - **Techniques**: Sketching, storyboarding, Crazy 8s, Heat Map voting, user testing - **Time**: 5 full days (can compress to 2-3 days) - **Output**: Validated prototype, user feedback, go/no-go decision - **When**: Big design decision, high uncertainty, time to test before committing **Pattern 6: Asynchronous Collaboration (Remote/Distributed)** - **Goal**: Collaborate across time zones, allow reflection time - **Format**: Post prompt → async responses (24-48h) → sync synthesis session → document - **Techniques**: Shared docs, threaded discussions, Loom videos, async voting (Polly, Simple Poll) - **Time**: 2-5 days total (30-60 min sync session) - **Output**: Documented decisions, rationale, action items - **When**: Global team, deep thinking needed, no urgency for immediate decision ## Guardrails 1. **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. 2. **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. 3. **Separate divergence from convergence**: Defer judgment during brainstorming, because critiquing ideas early kills creativity. Generate first, evaluate second. 4. **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. 5. **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. 6. **Decide how decisions are made**: Consensus, consent, majority vote, or delegation. Announce the method upfront to avoid "I thought we decided, but nothing happened." 7. **Track outputs visibly**: Shared board, live doc, or sticky notes so everyone sees the same thing. Assign a scribe. Invisible outputs are easily lost. 8. **Close with clarity**: State what was decided, who does what by when, what is still open, and how the group will communicate. **Common pitfalls:** - ❌ **No agenda**: Meetings drift, go long, participants unclear on purpose. Always have agenda (even 3 bullets). - ❌ **Wrong people**: Decision-makers absent, too many observers, missing key stakeholders. Right people > right process. - ❌ **Too much content**: 10 topics in 60 min = shallow on all. Better: 2-3 topics, go deep, make progress. - ❌ **Facilitator dominates**: Facilitator should guide process, not content. Reduce own talking, ask questions, stay neutral. - ❌ **No breaks**: 2+ hours without break → diminishing returns. Break every 60-90 min (5-10 min). - ❌ **Ignoring energy**: Pushing through low energy → poor output. Use energizers, adjust pace, or stop early. ## Quick Reference **Key resources:** - **[resources/template.md](resources/template.md)**: Session design template, agenda builder, logistics checklist, closing template - **[resources/methodology.md](resources/methodology.md)**: Pattern sele
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.