Skip to content
UX Design

Design Workshop Facilitation

Brian

Facilitate a workshop around a concrete decision with balanced participation and documented follow-up.

SKILL.md

---
name: knoveya-design-workshop-facilitation
description: "Facilitate a workshop around a concrete decision with balanced participation and documented follow-up. Use for matching ux design work."
---

# Design Workshop Facilitation

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Facilitate a workshop around a concrete decision with balanced participation and documented follow-up.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

The session ends with ownership, not only sticky notes.

## Example task

Run independent idea generation before group convergence.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-design-workshop-facilitation as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-design-workshop-facilitation/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Run independent idea generation before group convergence.

Verify

The session ends with ownership, not only sticky notes.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.