跳到正文
cccskills
免费在 GitHub 公开

codexkit-workshop-facilitator

Design and facilitate structured workshops using Design Thinking and Liberating Structures. Produces detailed agendas with time blocks, facilitation notes, participant materials, and retrospective templates. Use when running ideation sessions, retrospectives, planning workshops, or collaborative problem-solving.

中文简介正在准备中。当前显示原文说明。

集成工具Miro
查看安装方法

包含的文件(2)

  • SKILL.md5.6 KB
  • agents/openai.yaml166 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Workshop Facilitator

When to Use

  • When planning a brainstorming or ideation workshop
  • When facilitating strategy or planning sessions
  • When running collaborative problem-solving sessions
  • When designing team-building or training workshops

Procedure

Step 1 — Workshop Design Brief

ElementDetails
ObjectiveWhat must be achieved by the end?
ParticipantsWho, how many, their roles
DurationTotal time available
FormatIn-person / Virtual / Hybrid
Pre-workWhat participants should prepare
OutputsTangible deliverables from the session

Step 2 — Activity Selection

Match activities to objectives:

ObjectiveActivityTimeFormat
Generate ideasCrazy 8s, Brainwriting20 minIndividual → Group
PrioritizeDot voting, 2×2 Matrix15 minGroup
Explore problems5 Whys, Fishbone25 minSmall group
Align on visionFuture Backwards30 minFull group
Build consensus1-2-4-All (Liberating Structures)15 minProgressive
Define actionsRACI + Action planning20 minGroup
ReflectPlus/Delta, Sailboat retro15 minIndividual → Group

Step 3 — Agenda with Time Blocks

Build the full agenda:

TimeDurationActivityMethodMaterials
09:0010 minWelcome & check-inRound robinNone
09:105 minSet objectives & ground rulesFacilitatorSlide
09:1520 minProblem framing1-2-4-AllSticky notes
09:3525 minIdeationCrazy 8sPaper templates
10:0010 min☕ Break——
10:1020 minShare & clusterAffinity mappingWall/Miro
10:3015 minPrioritizeDot voting (3 dots each)Dot stickers
10:4520 minAction planningRACI templateWorksheet
11:0510 minRetro & closePlus/DeltaCards

Rules:

  • Never schedule >90 min without a break
  • Alternate individual → pair → group activities
  • End 10 min early for retro, never skip it

Step 4 — Facilitation Notes

For each activity, prepare:

  • Setup instructions — how to explain it
  • Timing cues — when to move to next phase
  • Energy watch — how to re-energize if energy drops
  • Divergence/Convergence — clearly label which mode
  • Silent before spoken — always start with individual reflection

Step 5 — Participant Materials

Prepare and distribute:

  • Pre-read or context document
  • Templates / worksheets
  • Miro board (virtual) or wall setup (in-person)
  • Ground rules card

Step 6 — Post-Workshop

  • Photo/screenshot all outputs
  • Synthesize into action items within 24 hours
  • Send summary + actions to all participants
  • Run Plus/Delta retro on the workshop format itself

Inputs

InputRequiredFormat
Workshop objectiveYesWhat must be achieved
ParticipantsYesWho, how many
DurationYesHours available
FormatYesIn-person / Virtual / Hybrid
ContextRecommendedBackground reading for participants

Output

## Workshop Plan — [Workshop Name]

### Overview
**Objective:** Generate and prioritize Q3 product roadmap ideas
**Participants:** Product (4), Engineering (4), Design (2) — 10 people
**Duration:** 2.5 hours | **Format:** Virtual (Miro)

### Agenda
[Full time-blocked agenda with activities and materials]

### Facilitator Guide
[Setup instructions and timing cues per activity]

### Participant Pre-Work
- Review Q2 metrics dashboard (link)
- Bring 3 customer pain points from your domain

### Materials
- Miro board: [link]
- Priority matrix template: [link]

Definition of Done

  • Clear objective and outputs defined
  • Agenda time-blocked with breaks
  • Activities matched to objectives
  • Facilitation notes for each activity
  • Participant materials prepared
  • Post-workshop action plan template ready

Quality Criteria

  • All placeholder sections are filled with domain-specific content
  • Structure follows the relevant industry standard or framework
  • Language matches target audience (technical / executive / legal)
  • Output is ready for review — not a rough draft requiring major rework

Verification (4C)

CheckQuestion
CorrectnessDoes the draft structure follow the stated framework or industry standard?
CompletenessAre all required sections present with substantive (not placeholder) content?
Context-fitDoes tone, detail level, and terminology match the intended audience?
ConsequenceIf sent to the intended recipient without further editing, what would fail?

Edge Cases

  • No existing template for this type — Use the closest available template and document all customizations made.
  • Stakeholder requirements conflict — Flag conflicts explicitly in the draft. Do not silently choose one requirement over another.
  • Output required in multiple formats — Produce the canonical format first, then derive others. Note any formatting limitations.

Changelog

  • v1.0.0 — Initial release

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

查看 hoavdc 的全部技能

报告此技能的问题