Agent Skills
› mohitagw15856/pm-claude-skills
› workshop-designer
workshop-designer
GitHub设计以产出具体成果为导向的工作坊，通过逆向规划、静默写作及结构化收敛机制，避免无效讨论。提供从目标定义到活动序列、引导笔记及成果捕获的完整设计方案。
Trigger Scenarios
设计工作坊
策划规划会议
组织半天工作会议
解决工作坊有趣但无产出的问题
Install
npx skills add mohitagw15856/pm-claude-skills --skill workshop-designer -g -y
SKILL.md
Frontmatter
{
"name": "workshop-designer",
"homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/workshop-designer.html",
"metadata": {
"openclaw": {
"emoji": "🧠"
}
},
"description": "Design working sessions that produce artifacts, not vibes — the outcome-backwards agenda, the activity formats that beat open discussion (silent writing, dot voting, structured rounds), the energy arc, and the output-capture that survives the room. Use when asked design a workshop for X, plan our planning session, facilitate a half-day working session, or our workshops are fun but nothing comes out. Produces the workshop design: the artifact goal, the activity sequence with timings, the facilitation notes, and the capture plan."
}
Workshop Designer Skill
Workshops fail pleasantly: good discussion, full whiteboards, warm feelings — and nothing anyone can use on Monday. The fix is designing backwards from the artifact: name the thing the room must produce (a prioritized list, a draft charter, three concept sketches, an agreed map), then choose activities that manufacture it — and open discussion is almost never that activity, because it's dominated by the confident and produces talk, not output. Silent writing, structured rounds, and forced ranking exist precisely because they extract from everyone and converge on paper.
What This Skill Produces
- The artifact spec — what the workshop produces, concretely, and who uses it afterward
- The activity sequence — timeboxed blocks, each transforming the previous block's output toward the artifact
- The facilitation notes — per block: instructions verbatim, the timekeeping, the dominance-management moves
- The capture plan — how outputs leave the room usable (photographed, transcribed, owned) — the step every fun workshop skips
Required Inputs
Ask for these if not provided:
- The artifact — pushed to concrete: "alignment on strategy" becomes "a one-page strategy statement the leads will sign" (outline-before-prose claim-discipline applies to workshop goals too)
- The cast — headcount, seniority mix, the known dominators and the known silents (the design manages both), remote/hybrid reality
- The time box and the room — 90 minutes designs differently than a day; hybrid needs its own mechanics (boards everyone can touch)
- The pre-work tolerance — what the group will actually do beforehand (honest answer: little — design for it)
Framework: The Design Rules
- Backwards from the artifact: write the artifact spec first, then ask "what's the last activity that produces it?" and chain backwards — every block's output is the next block's input, and any block whose output feeds nothing gets cut. Agendas built forward accumulate activities; backwards they earn them.
- Silent writing beats brainstorming: individual writing first (everyone produces, nobody anchors), then share-and-cluster — this one substitution fixes the dominance problem, the anchoring problem, and the quiet-expert problem simultaneously. Structured rounds (each person, 60 seconds, no responses) do the same for discussion.
- Converge with mechanisms, not debate: dot votes, forced ranking, 2×2 placement — convergence tools that produce a visible ordered result in minutes. Debate converges at the speed of stamina; mechanisms converge at the speed of the timebox — debate then happens richly on the top-3, where it's worth its cost.
- Design the energy arc: hard divergence early (fresh minds), mechanical convergence mid, decisions before the last block (never in it — tired rooms decide badly), and breaks before the room needs them. After-lunch blocks are active or they're naps with agendas.
- Capture is a role, not an afterthought: one named person photographs boards, transcribes clusters, and records decisions as they happen — and the workshop's last ten minutes assign every output an owner and a date in front of the room. The artifact spec is met when the usable version exists outside the room, same day.
Output Format
Workshop: [artifact] — [duration], [N] people
The Artifact Spec
[What exists at the end · who uses it Monday · the sign-of-success]
The Sequence
| Time | Block | Format | Output → feeds |
|---|---|---|---|
| [Diverge (silent-first) → cluster → converge (mechanism) → decide (pre-fatigue) → assign] |
Facilitation Notes
[Per block: verbatim instructions · the dominance moves (rounds, parking lot) · hybrid mechanics if needed]
Capture Plan
[The capture role (named) · boards → digital same-day · the last-10-minutes owner-and-date assignment]
Quality Checks
- The artifact is concrete and its Monday user is named
- Every block's output feeds the next; orphan activities were cut
- Divergence starts silent; convergence uses mechanisms
- Decisions land before the final-hour fatigue
- Capture has a named owner and outputs leave the room same-day
Anti-Patterns
- Do not design forward from fun activities — backwards from the artifact or it's team-building in disguise (which is fine, but name it)
- Do not open with group brainstorming — silent writing first, always
- Do not converge by discussion — mechanisms converge; discussion enriches the converged
- Do not schedule deciding last — tired rooms defer or decide badly
- Do not let the boards die in the room — un-captured workshops happened only emotionally
Version History
- 471c606 Current 2026-07-22 13:49
