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에서 보기