Collaborative domain modeling through pictographic stories. Use when gathering requirements, understanding business workflows, onboarding team members, or preparing for event storming. Follows Stefan Hofer & Henning Schwentner's methodology with actors, work objects, and activities.
View on GitHubmelodic-software/claude-code-plugins
enterprise-architecture
plugins/enterprise-architecture/skills/domain-storytelling/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/enterprise-architecture/skills/domain-storytelling/SKILL.md -a claude-code --skill domain-storytellingInstallation paths:
.claude/skills/domain-storytelling/# Domain Storytelling Skill ## Overview Domain Storytelling is a collaborative modeling technique that captures business processes through pictographic stories. This skill guides AI-assisted domain storytelling sessions that can feed into event storming and bounded context discovery. **Key Principle:** Stories are told from the perspective of domain experts, using their language and understanding. ## When to Use This Skill **Keywords:** domain storytelling, pictographic, actors, work objects, activities, AS-IS, TO-BE, business workflow, domain modeling, story collection, bounded context discovery, requirements gathering **Use this skill when:** - Gathering requirements from domain experts - Understanding existing business workflows (AS-IS) - Designing future state processes (TO-BE) - Onboarding team members to a domain - Preparing for event storming sessions - Identifying bounded context candidates - Building a ubiquitous language glossary ## Story Types ### AS-IS Stories Document how things work **today**: - Current state processes - Existing pain points - Workarounds and exceptions - Real behavior (not idealized) **When to use:** Understanding current state, identifying problems, baseline before changes. ### TO-BE Stories Document how things **should work**: - Desired future state - Improved processes - New capabilities - Idealized flow (but achievable) **When to use:** Requirements gathering, designing solutions, communicating vision. ## Pictographic Language Domain Storytelling uses simple pictographic elements: | Element | Symbol | Description | | --- | --- | --- | | **Actor** | 🧑 (stick figure) | Person or system that performs activities | | **Work Object** | 📄 (document) | Data, documents, or physical items exchanged | | **Activity** | ➡️ (arrow with verb) | Action performed by an actor | | **Sequence** | ① ② ③ | Numbered order of activities | | **Annotation** | 💬 (note) | Additional context or explanation | **Detailed notation guide:**