agentleFS
wilstowilsto/claude-code-starter-kit/.claude/skills/workshop-facilitation/SKILL.md

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

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

    One-step-at-a-time: Ask a single targeted question per turn.

    line 14
  2. Very specific:

    Session heads-up + entry mode: Start by setting expectations and offering Guided, Context dump, or Best guess mode.

    line 15
  3. Common:

    Decision-point recommendations: Use enumerated options only when a choice is needed, not after every answer.

    line 17
  4. Common:

    Fast path: If the user requests a single-shot output, skip multi-turn facilitation and deliver a condensed result.

    line 22
  5. Common:

    Start with a brief heads-up on estimated time and number of questions.

    line 25
  6. Common:

    Ask the user to choose an entry mode:

    line 26
  7. Common:

    Run one question per turn and wait for an answer before continuing.

    line 30
  8. Common:

    Keep questions plain-language.

    line 31
  9. Common:

    Ask follow-up clarifications only when they materially improve recommendation quality.

    line 35
  10. Common:

    Keep options concise and mutually exclusive when possible.

    line 37
  11. Common:

    after maturity/profile synthesis,

    line 42
  12. Common:

    If interrupted by a meta question, answer directly, then restate progress and pending question.

    line 45
  13. Common:

    If the user says stop/pause, halt immediately and wait for explicit resume.

    line 46
  14. Common:

    Use as the source of truth for interactive facilitation behavior.

    line 78

“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

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, or Best guess mode.
  • Progress visibility: Show user-facing progress labels like Context Qx/8 and Scoring 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

  1. Start with a brief heads-up on estimated time and number of questions.
  2. Ask the user to choose an entry mode:
    • 1 Guided mode (one question at a time)
    • 2 Context dump (paste known context; skip redundancies)
    • 3 Best guess mode (infer missing details and label assumptions)
  3. Run one question per turn and wait for an answer before continuing.
  4. Keep questions plain-language; include a short example response format when helpful.
  5. Show progress each turn:
    • Context Qx/8 during context collection
    • Scoring Qx/5 during assessment/scoring
  6. Ask follow-up clarifications only when they materially improve recommendation quality.
  7. 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,3 or 1 and 3.
  8. Provide numbered recommendations only at decision points:
    • after context synthesis,
    • after maturity/profile synthesis,
    • during priority/action-plan selection.
  9. Accept numeric or custom choices, synthesize multi-select choices, and continue.
  10. If interrupted by a meta question, answer directly, then restate progress and pending question.
  11. If the user says stop/pause, halt immediately and wait for explicit resume.
  12. End with a clear summary, decisions made, and (if best guess mode was used) an Assumptions to Validate list.

Examples

Opening: "Quick heads-up: this should take about 7-10 minutes and around 10 questions. How do you want to start?

  1. Guided mode
  2. Context dump
  3. 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:

  1. Prioritize Context Design (Recommended)
  2. Prioritize Agent Orchestration
  3. 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, *-prep skills).
  • Credit: Dean Peters, Product Manager Skills (CC BY-NC-SA 4.0).

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.