run-a-design-workshop
Facilitate a bounded design decision with shared evidence and explicit authority. Use when contributors need to understand a problem, generate options, expose tradeoffs, and leave with an owned next step.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- run-a-design-workshop
- category
- design
- description
- Facilitate a bounded design decision with shared evidence and explicit authority. Use when contributors need to understand a problem, generate options, expose tradeoffs, and leave with an owned next step.
# run-a-design-workshop
## Procedure
1. Define the decision, authority, inputs, participants, access needs, outputs, and non-goals.
2. Share a concise evidence pack and prework with enough time for access.
3. Design an agenda that separates facts, framing, divergence, evaluation, and decision.
4. Include people with user, delivery, technical, operational, accessibility, and policy knowledge as needed.
5. State facilitation rules and prevent seniority from silently becoming evidence.
6. Capture ideas before group convergence and retain dissent.
7. Evaluate options against predeclared criteria, constraints, and unknowns.
8. Close with decision, experiment, owner, date, evidence, and unresolved questions.
9. Send a workshop record and verify participant corrections.
## Guardrails
- Do not use a workshop to manufacture consent for a decided outcome.
- Protect confidential research and personal information.
- Participation does not transfer decision accountability.
## Done
- A workshop plan and record preserve evidence, options, decision, dissent, and owners
- Accessibility and participation checks are completed
- Next-step acceptance criteria are scheduled
GitHubで見る