Workshop design — event storming, impact mapping, user story mapping, design sprints. Use when the user asks to "plan a workshop", "run event storming", "facilitate impact mapping", "design a sprint", "create user story map", "facilitate discovery session", or mentions workshop facilitation, 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/prompt.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.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Workshop facilitation designs and runs 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.
Un taller mal facilitado no solo desperdicia tiempo — destruye la confianza del equipo en los procesos colaborativos. La facilitación excelente es la diferencia entre alineamiento genuino y consenso superficial.
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)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.
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.
| Caso | Estrategia de Manejo |
|---|---|
| Key domain expert is unavailable for the scheduled workshop | Postpone the session if the expert's knowledge is critical (event storming without domain experts produces developer assumptions); alternatively, run a preliminary session and mark all outputs as [SUPUESTO] pending expert validation |
| Workshop participants speak different languages (e.g., Spanish + English + Portuguese) | Designate bilingual facilitators per breakout group; use visual artifacts (stickies, diagrams) as the primary communication medium; provide translated templates for key activities |
| Hybrid workshop (some in-person, some remote) | Assign a dedicated "bridge facilitator" to ensure remote participants have equal voice; use a shared digital board as the canonical artifact even for in-person participants; run explicit check-ins with remote attendees every 20 minutes |
| Workshop output contradicts prior discovery phase findings | Document the contradiction explicitly; do not suppress either version; flag for steering committee arbitration; the workshop may have surfaced tacit knowledge that prior analysis missed |
| Decision | Alternativa Descartada | Justificacion |
|---|---|---|
| Silent-before-spoken rule for all ideation activities | Open discussion from the start | Open discussion allows dominant voices to anchor the group; 5-10 minutes of silent individual writing produces broader, more diverse input that discussion then refines |
| Maximum 8 participants per workshop session (breakouts for larger groups) | Allow 15+ participants in a single session | Groups larger than 8 suffer from diffusion of responsibility and reduced psychological safety; breakouts with sub-facilitators maintain quality and participation |
| Diverge-Converge rhythm as mandatory structure for every activity | Emergent facilitation that follows energy | Emergent facilitation works only with expert facilitators; the diverge-converge structure provides guardrails that produce consistent quality regardless of facilitator experience |
graph TD
subgraph Core["Workshop Facilitator"]
A["Technique Selection"] --> B["Session Design"]
B --> C["Facilitation Guide"]
C --> D["Live Facilitation"]
D --> E["Synthesis & Handoff"]
end
subgraph Inputs["Inputs"]
F["Workshop Goal"] --> A
G["Participant List"] --> B
H["Prior Discovery Artifacts"] --> A
end
subgraph Outputs["Outputs"]
E --> I["Workshop Design Document"]
E --> J["Action Items + Decision Log"]
E --> K["Artifact Package"]
end
subgraph Related["Related Skills"]
L["functional-spec"] -.-> E
M["scenario-analysis"] -.-> A
end
A-01_Workshop_Design_{cliente}_{WIP}.mdA-01_Workshop_Design_{cliente}_{WIP}.html{fase}_{entregable}_{cliente}_{WIP}.docx{fase}_workshop-facilitator_{cliente}_{WIP}.xlsx{fase}_{entregable}_{cliente}_{WIP}.pptx| Dimension | Peso | Criterio |
|---|---|---|
| Trigger Accuracy | 10% | Descripcion activa triggers correctos sin falsos positivos |
| Completeness | 25% | Todos los entregables cubren el dominio sin huecos |
| Clarity | 20% | Instrucciones ejecutables sin ambiguedad |
| Robustness | 20% | Maneja edge cases y variantes de input |
| Efficiency | 10% | Proceso no tiene pasos redundantes |
| Value Density | 15% | Cada seccion aporta valor practico directo |
Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.
Autor: Javier Montaño | Ultima actualizacion: 15 de marzo de 2026