workshop-facilitation
Skill0 starsChanged 8 months agoMITView on GitHub
Canonical facilitation protocol for interactive skills: one-step-at-a-time flow with numbered recommendations at decision points and quick-select options. Triggers: referenced automatically by interactive skills.
11 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- fralapo/awesome-agent-skillstheir own version, first seen Nov 8, 2026
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillsedited, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillsedited, first seen Oct 25, 2026
- The-Utopia-Studio/skillsedited, first seen Oct 13, 2026
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- deanpeters/Product-Manager-Skills★ 7.7k65% same
- DIAL-Studio/pm-agent-harness-kit★ 1246% same
- The-Utopia-Studio/skills★ 682% same
- agrivisionai/claude-skills★ 165% same
- NinjaSln-labs/agent-skills★ 144% same
- vijaysuperpositionist/skills★ 082% same
Wrote their own version · 5
- anotb/management-consulting-plugin★ 62same name
- henrique-simoes/Istara★ 15same name
- fralapo/awesome-agent-skills★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- Samueladewole/claude-skills★ 0same name
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 repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ci-watchSkill
- commitSkill
- discovery-interview-prepSkill
- doc-generateSkill
- incident-responseSkill
- opportunity-solution-treeSkill
- polarisSkill
- prd-developmentSkill
- prioritization-advisorSkill
- reviewSkill
- roadmapSkill
- security-auditSkill
- session-wrapSkill
- spec-updateSkill
- tddSkill
- tech-debt-auditSkill
- test-runnerSkill
- user-storySkill
- uxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 13 are common, 0 are distinctive, and 1 is very specific to this project.
13
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 14
One-step-at-a-time: Ask a single targeted question per turn.
- Very specific: line 15
Session heads-up + entry mode: Start by setting expectations and offering Guided, Context dump, or Best guess mode.
- Common: line 17
Decision-point recommendations: Use enumerated options only when a choice is needed, not after every answer.
- Common: line 22
Fast path: If the user requests a single-shot output, skip multi-turn facilitation and deliver a condensed result.
- Common: line 25
Start with a brief heads-up on estimated time and number of questions.
- Common: line 26
Ask the user to choose an entry mode:
- Common: line 30
Run one question per turn and wait for an answer before continuing.
- Common: line 31
Keep questions plain-language.
- Common: line 35
Ask follow-up clarifications only when they materially improve recommendation quality.
- Common: line 37
Keep options concise and mutually exclusive when possible.
- Common: line 42
after maturity/profile synthesis,
- Common: line 45
If interrupted by a meta question, answer directly, then restate progress and pending question.
- Common: line 46
If the user says stop/pause, halt immediately and wait for explicit resume.
- Common: line 78
Use as the source of truth for interactive facilitation behavior.
“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
Purpose
Provide the canonical facilitation pattern for interactive skills: one step at a time, with clear progress, adaptive recommendations at decision points, and predictable interruption handling.
Key Concepts
- One-step-at-a-time: Ask a single targeted question per turn.
- Session heads-up + entry mode: Start by setting expectations and offering
Guided,Context dump, orBest guessmode. - Progress visibility: Show user-facing progress labels like
Context Qx/8andScoring Qx/5. - Decision-point recommendations: Use enumerated options only when a choice is needed, not after every answer.
- Quick-select response options: For regular context/scoring questions, provide concise numbered answer options plus
Other (specify)when useful. - Flexible selection parsing: Accept
#1,1,1 and 3,1,3, or custom text, then synthesize multi-select choices. - Context-aware progression: Build on previous answers and avoid re-asking resolved questions.
- Interruption-safe flow: Answer meta questions directly (for example, "how many left?"), restate status, then resume.
- Fast path: If the user requests a single-shot output, skip multi-turn facilitation and deliver a condensed result.
Application
- Start with a brief heads-up on estimated time and number of questions.
- Ask the user to choose an entry mode:
1Guided mode (one question at a time)2Context dump (paste known context; skip redundancies)3Best guess mode (infer missing details and label assumptions)
- Run one question per turn and wait for an answer before continuing.
- Keep questions plain-language; include a short example response format when helpful.
- Show progress each turn:
Context Qx/8during context collectionScoring Qx/5during assessment/scoring
- Ask follow-up clarifications only when they materially improve recommendation quality.
- For regular context/scoring questions, offer quick-select numbered response options when practical:
- Keep options concise and mutually exclusive when possible.
- Include
Other (specify)if likely answers are open-ended. - Accept multi-select responses like
1,3or1 and 3.
- Provide numbered recommendations only at decision points:
- after context synthesis,
- after maturity/profile synthesis,
- during priority/action-plan selection.
- Accept numeric or custom choices, synthesize multi-select choices, and continue.
- If interrupted by a meta question, answer directly, then restate progress and pending question.
- If the user says stop/pause, halt immediately and wait for explicit resume.
- End with a clear summary, decisions made, and (if best guess mode was used) an
Assumptions to Validatelist.
Examples
Opening: "Quick heads-up: this should take about 7-10 minutes and around 10 questions. How do you want to start?
- Guided mode
- Context dump
- Best guess mode"
User: "2"
Facilitator: "Paste what you already know. I'll skip answered areas and ask only what's missing."
Decision point after synthesis:
- Prioritize Context Design (Recommended)
- Prioritize Agent Orchestration
- Prioritize Team-AI Facilitation
User: "1 and 3"
Facilitator: "Great. We'll run Context Design first, with Team-AI Facilitation in parallel."
Common Pitfalls
- Asking multiple questions in the same turn.
- Offering recommendations after every answer (creates interaction drag).
- Using shorthand labels without plain-language questions.
- Hiding progress, so users don't know how much remains.
- Ignoring the user's chosen option or custom direction.
- Failing to label assumptions when running in best-guess mode.
References
- Use as the source of truth for interactive facilitation behavior.
- Apply alongside all interactive skills (
*-advisor,*-workshop,*-prepskills). - Credit: Dean Peters, Product Manager Skills (CC BY-NC-SA 4.0).
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.

