workshop-facilitation

Overview of workshop-facilitation skill

The workshop-facilitation skill is a facilitation pattern for interactive, multi-turn workshops where the AI needs to ask one question, track progress, and adapt at decision points without overwhelming the user. It is best for product managers, facilitators, and builders who want a structured workshop flow instead of a loose conversational prompt.

What users usually care about is not “can it chat,” but whether it can keep a session moving, surface the right choices at the right time, and recover cleanly when the user interrupts or changes direction. The workshop-facilitation skill is designed for that job-to-be-done.

What this skill is good for

Use the workshop-facilitation skill when you need:

• a guided workshop with numbered options and clear next steps
• progress labels that make long sessions feel manageable
• predictable handling of partial answers, interruptions, and pivots
• a repeatable structure for PM workshops, discovery sessions, and decision meetings

What makes it different

Unlike a generic prompt, the workshop-facilitation skill emphasizes pacing and session control:

• one focused question per turn
• decision points only when a choice is needed
• visible progress so users know where they are
• a mode selection up front, such as Guided, Context dump, or Best guess

When it is a strong fit

This is a good install if your workflow templates depend on interactive gathering, synthesis, or scoring across several steps. It is especially useful for workshop-facilitation for Workflow Templates where consistency matters more than freeform brainstorming.

How to Use workshop-facilitation skill

Install and first files to read

For workshop-facilitation install, add the skill from the repository path and then inspect the canonical instruction file first:

1. npx skills add deanpeters/Product-Manager-Skills --skill workshop-facilitation
2. Open skills/workshop-facilitation/SKILL.md
3. Review the full file tree for any linked materials, even though this repo has no extra rules/, resources/, or scripts

If you only skim one file, make it SKILL.md; it contains the facilitation contract, the session modes, and the progress logic.

How to prompt it well

A strong workshop-facilitation usage request should say:

• the workshop goal
• the audience or participants
• the decision you want at the end
• the time or round limit
• the mode you want, if you have one

Example input shape:

• “Run a discovery workshop for a B2B PM team. I need 6 questions, a final summary, and options when tradeoffs appear. Use Guided mode.”
• “Facilitate a prioritization session for three features. Keep progress visible and stop after scoring.”
• “Help me run a positioning workshop. I’ll provide rough notes; ask one question at a time.”

Practical workflow

The best workshop-facilitation guide workflow is:

1. Start with the session goal and choose an entry mode.
2. Let the skill ask one question before adding more context.
3. Answer in short, concrete chunks.
4. Accept enumerated recommendations only at decision points.
5. Ask for a recap or next-step summary at the end.

This structure matters because the skill is optimized for controlled momentum, not for dumping everything into one message.

Tips that improve output quality

Provide specifics that reduce back-and-forth:

• the workshop type
• the desired output artifact
• constraints such as time, audience size, or decision rules
• what counts as a successful end state

Avoid starting with vague commands like “facilitate this workshop.” That forces the skill to infer too much and weakens the session flow.

workshop-facilitation skill FAQ

Is workshop-facilitation only for product teams?

No. It is strongest for product and strategy workshops, but the same pattern works for research synthesis, planning sessions, review meetings, and any guided decision process that benefits from one-step-at-a-time pacing.

Do I need a template to use it?

No, but workshop-facilitation for Workflow Templates is where it shines. If you already have a repeatable workshop format, this skill helps you run it consistently and keep participants oriented.

How is this different from a normal prompt?

A normal prompt may answer quickly, but the workshop-facilitation skill is built to manage the interaction itself: session framing, controlled questioning, progress labels, and decision-point branching. That makes it more reliable for multi-turn workshops than a one-off instruction.

When should I not use it?

Do not use it if you want a single-shot answer, a static document, or a fully automated summary with no interaction. If the task does not require guided turn-taking, a simpler prompt is usually better.

How to Improve workshop-facilitation skill

Give the skill a clearer target

The biggest improvement comes from stating the end artifact up front. Say whether you want a decision, a shortlist, a workshop summary, a scoring matrix, or a set of next steps. The more concrete the target, the better workshop-facilitation usage performs.

Add constraints that shape the session

The skill works better when you include:

• timebox or number of rounds
• participant context
• decision criteria
• any must-cover topics
• what to do when answers are incomplete

These details help the skill choose the right level of structure without over-questioning.

Watch for common failure modes

Most weak sessions come from one of three issues:

• too much context in the first turn
• unclear success criteria
• skipping the decision points and asking for conclusions too early

If the session feels muddy, tighten the opening prompt and ask the skill to continue one step at a time.

Iterate after the first run

After the first output, improve the next round by telling the skill what was missing:

• “Ask fewer follow-ups and move to options sooner.”
• “Make progress labels shorter.”
• “Use stricter scoring before recommendations.”
• “Summarize after every three questions.”

That kind of feedback helps the workshop-facilitation skill adapt to your preferred facilitation style without losing structure.