Workshop design methodology — event storming, impact mapping, user story mapping, design sprints. Replaces former workshop-facilitator (facilitation is the agent's job, design is the skill). Use when the user asks to "design a workshop", "plan event storming", "design impact mapping session", "design a sprint", "create user story map", "design discovery session", or mentions workshop design, design sprint, event storming, story mapping, or collaborative design.
From pmnpx claudepluginhub javimontano/mao-pm-apexThis skill is limited to using the following tools:
examples/README.mdexamples/sample-output.htmlexamples/sample-output.mdprompts/metaprompts.mdprompts/use-case-prompts.mdreferences/body-of-knowledge.mdreferences/knowledge-graph.mmdreferences/state-of-the-art.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Workshop design creates structured collaborative sessions to extract knowledge, align stakeholders, and produce actionable artifacts. Covers technique selection, session design, facilitation guides, and synthesis — from event storming to design sprints.
A poorly facilitated workshop does not just waste time — it destroys the team's trust in collaborative processes. Excellent facilitation is the difference between genuine alignment and superficial consensus.
The user provides a project or workshop goal as $ARGUMENTS. Parse $1 as the project/workshop name used throughout all output artifacts.
Before generating workshop design, detect project context:
find . -name "*.md" -o -name "*.miro" -o -name "*.figjam" -o -name "*.pdf" -o -name "workshop*" | head -20
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40%) | técnica (full, default){MODO_OPERACIONAL}: integral (default, complete workshop design + synthesis) | facilitacion (energy management, diverge/converge cycles, breaks, energizers, facilitation timeline) | sintesis (output consolidation, deduplication, thematic clustering, owner assignment, action items)Matches the right technique to the workshop goal, selects participants, and designs the agenda.
Technique selection matrix:
Core facilitation principles:
Key decisions:
Discovers domain knowledge by exploring events, commands, aggregates, and bounded contexts.
Includes:
Connects business goals to deliverables through actors and impacts.
Includes:
Organizes user activities into a backbone and plans releases as horizontal slices.
Includes:
Compressed prototyping and validation cycle — understand, sketch, decide, prototype, test.
Includes:
Consolidates workshop outputs into actionable artifacts and establishes follow-up cadence.
Includes:
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Event Storming | Deep domain understanding, DDD alignment | Requires domain experts, time-intensive | Complex domains, DDD projects |
| Impact Mapping | Goal alignment, scope negotiation | Abstract, requires clear business goal | Strategy-to-execution alignment |
| User Story Mapping | Release planning, shared understanding | Requires known user journey | Agile planning, MVP definition |
| Design Sprint | Fast validation, reduced risk | Requires 5 days, facilitator skill | New products, risky features |
| Full-Day Workshop | Deep exploration, relationship building | Calendar cost, energy management | Kickoffs, complex problems |
| Compressed Format | Time-efficient, lower commitment | Shallow output, risk of rushing | Follow-ups, well-scoped questions |
Remote-Only Team: Use Miro, FigJam, or Excalidraw. Shorter sessions (2-3 hours max). More structured facilitation. Breakout rooms for parallel work. Maintain dual-agenda: external schedule for participants and internal facilitator script.
Remote Facilitation Anti-Patterns (avoid):
Large Group (15+): Split into breakout groups of 4-6. Assign sub-facilitators. Gallery walks and dot voting for convergence.
Conflicting Stakeholders: Surface conflicts explicitly. Use structured techniques (silent brainstorming, anonymous voting) to reduce power dynamics. Facilitator must be neutral.
Domain Experts Unavailable: Event storming without domain experts produces developer assumptions. Either postpone or run preliminary session marking assumptions explicitly.
Workshop Fatigue: Demonstrate follow-through. Keep session shorter, action-oriented. Show how prior outputs were used.
| Caso | Estrategia de Manejo |
|---|---|
| Equipo 100% remoto sin experiencia en talleres colaborativos | Usar Miro/FigJam; sesiones mas cortas (2-3h max); facilitacion mas estructurada con templates pre-llenados; breaks cada 40 min; instrucciones escritas en cada actividad |
| Grupo grande (15+ participantes) sin posibilidad de reducir | Dividir en breakout groups de 4-6; asignar sub-facilitadores; usar gallery walks y dot voting para convergencia; evitar plenarias extensas |
| Domain experts no disponibles para event storming | Posponer event storming o ejecutar sesion preliminar marcando supuestos explicitamente; el output sin domain experts es developer assumptions, no domain knowledge |
| Fatiga de talleres en la organizacion (demasiados workshops sin follow-through) | Demostrar follow-through de sesiones anteriores; mantener sesiones cortas y orientadas a accion; mostrar como outputs anteriores fueron utilizados |
| Decision | Alternativa Descartada | Justificacion |
|---|---|---|
| Seleccionar tecnica segun objetivo del taller (event storming para dominio, impact mapping para scope, etc.) | Usar siempre la misma tecnica independiente del objetivo | Cada tecnica tiene un sweet spot; usar event storming para priorizar o design sprint para descubrir dominio produce resultados sub-optimos |
| Aplicar regla "silent-before-spoken" en toda ideacion | Comenzar directamente con discusion abierta | La ideacion silenciosa produce mas ideas diversas; la discusion abierta tiende a sesgo del mas vocal y groupthink |
| Disenar agenda con ritmo diverge-converge explicito | Agenda lineal sin ciclos de divergencia/convergencia | Sin convergencia, el taller produce ideas sin decisiones; sin divergencia, las ideas son limitadas por el pensamiento grupal |
graph TD
subgraph Core["Workshop Design Core"]
A[metodologia-workshop-design]
A1[S1: Selection & Design]
A2[S2: Event Storming]
A3[S3: Impact Mapping]
A4[S4: User Story Mapping]
A5[S5: Design Sprint]
A6[S6: Synthesis & Handoff]
end
subgraph Inputs["Inputs"]
I1[Workshop Goal]
I2[Participant List]
I3[Project Context Docs]
end
subgraph Outputs["Outputs"]
O1[Workshop Design Document]
O2[Facilitation Guide]
O3[Synthesis Report]
end
subgraph Related["Related Skills"]
R1[metodologia-stakeholder-mapping]
R2[metodologia-functional-toolbelt]
R3[metodologia-ux-design-discovery]
R4[metodologia-mentoring-training-discovery]
end
I1 --> A
I2 --> A
I3 --> A
A --> A1 --> A2
A1 --> A3
A1 --> A4
A1 --> A5
A2 --> A6
A3 --> A6
A4 --> A6
A5 --> A6
A --> O1
A --> O2
A --> O3
R1 --> A
A --> R2
A --- R3
A --- R4
Formato MD (default):
# Workshop Design — {nombre del taller}
## Objetivo
> Que se busca lograr y como se medira el exito.
## Tecnica Seleccionada
| Tecnica | Justificacion | Duracion | Participantes |
## Agenda Detallada
| Bloque | Actividad | Duracion | Facilitador | Output |
## Pre-work
[Materiales a enviar antes del taller]
## Guia de Facilitacion
[Script interno para el facilitador con time-boxes y transiciones]
## Template de Sintesis
[Estructura para consolidar outputs post-taller]
Formato DOCX (bajo demanda):
{fase}_{entregable}_{cliente}_{WIP}.docxFormato XLSX (bajo demanda):
{fase}_workshop-design_{cliente}_{WIP}.xlsxFormato PPTX (bajo demanda):
{fase}_{entregable}_{cliente}_{WIP}.pptxFormato HTML (para distribucion a participantes):
Header: Logo + nombre del taller + fecha
Section 1: Objetivo y Expectativas (callout box)
Section 2: Agenda Visual (timeline con bloques de color)
Section 3: Pre-work Required (checklist con links)
Section 4: Que Traer / Como Prepararse
Section 5: Logistics (lugar/link, horario, breaks)
Footer: Contacto del facilitador + MetodologIA attribution
--- Documento separado (interno): Facilitation Guide (no distribuir a participantes)
| Dimension | Peso | Criterio | Umbral Minimo |
|---|---|---|---|
| Trigger Accuracy | 10% | El skill se activa ante prompts de workshop design, event storming, impact mapping, design sprint, story mapping | 7/10 |
| Completeness | 25% | Tecnica seleccionada con justificacion; agenda time-boxed; pre-work definido; sintesis planificada; action items con owners | 7/10 |
| Clarity | 20% | Agenda es ejecutable por un facilitador sin contexto adicional; participantes entienden que se espera de ellos | 7/10 |
| Robustness | 20% | Edge cases cubiertos (remoto, grupo grande, sin experts, fatiga); anti-patterns de facilitacion remota documentados | 7/10 |
| Efficiency | 10% | Duracion y formato adaptados al contexto (no usar full-day cuando 2h es suficiente); modo operacional correcto | 7/10 |
| Value Density | 15% | Outputs del taller alimentan directamente actividades downstream; follow-up cadence definida; knowledge transfer para no-asistentes | 7/10 |
Umbral minimo global: 7/10. Si alguna dimension cae por debajo, el entregable requiere revision antes de entrega.
Before finalizing delivery, verify:
| Format | Default | Description |
|---|---|---|
markdown | ✅ | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter.
Primary: A-01_Workshop_Design.html — Technique selection rationale, detailed agenda, facilitation guide, participant briefing, synthesis template, action item tracker.
Formerly separate sub-agents (energy-manager, synthesis-engine) are now operational modes:
| Mode | Focus | Best For |
|---|---|---|
integral (default) | Complete workshop design: technique selection, agenda, facilitation, energy, synthesis | Standard discovery workshop design |
facilitacion | Energy management, diverge/converge cycles, strategic breaks, energizers, attention monitoring, energy arc | Optimizing engagement and productivity during the workshop |
sintesis | Raw output consolidation, deduplication, thematic clustering, contradiction resolution, action items with owners and deadlines | Post-workshop: transforming raw outputs into actionable deliverables |
Invoke with {MODO_OPERACIONAL}=facilitacion or {MODO_OPERACIONAL}=sintesis.