Workshop design — event storming, impact mapping, user story mapping, design sprints. [EXPLICIT] 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. [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/domain-knowledge.mdtemplates/output.docx.mdtemplates/output.htmlSearches 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.
Searches, 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.
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. [EXPLICIT]
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. [EXPLICIT]
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. [EXPLICIT]
Technique selection matrix:
Core facilitation principles:
Key decisions:
Discovers domain knowledge by exploring events, commands, aggregates, and bounded contexts. [EXPLICIT]
Includes:
Connects business goals to deliverables through actors and impacts. [EXPLICIT]
Includes:
Organizes user activities into a backbone and plans releases as horizontal slices. [EXPLICIT]
Includes:
Compressed prototyping and validation cycle — understand, sketch, decide, prototype, test. [EXPLICIT]
Includes:
Consolidates workshop outputs into actionable artifacts and establishes follow-up cadence. [EXPLICIT]
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. [EXPLICIT]
Primary: A-01_Workshop_Design.html — Technique selection rationale, detailed agenda, facilitation guide, participant briefing, synthesis template, action item tracker.
Author: Javier Montano | Last updated: 2026-03-12