client-scenario-story-mapping

Files (2)

• SKILL.md
• scenario-story-map-fr.md · templates/

SKILL.md (first lines)

# Client Scenario Story Mapping

Use this skill after the upstream discovery chain has already produced:
- a validated client profile
- a sector/market summary
- a business idea list
- a technical idea / feature list

## Goal

Transform the discovered features and business ideas into a large, structured scenario document that helps:
- imagine how the solution actually behaves in real life
- group features by user-experience logic
- discover missing pieces
- discover edge cases and abusive cases
- identify weak, rarely useful, or disconnected options
- prepare later architecture, scoping, and proposal work

This skill is intentionally expansive.
It should generate many stories, not just a neat short summary.
This run is expected to be heavy and token-intensive if needed.
The target is completeness and rigor, not brevity.

## Core principle

Do **not** try to solve everything in one monolithic pass.
Use fresh-context subagents or equivalent separate passes with clearly separated responsibilities.

This skill should be orchestrated as a multi-agent workflow whenever possible.
A single-agent fallback is acceptable, but the preferred mode is role-based decomposition.

Every story must try to resolve each problem or transition using an option already present in the discovered feature list.
If a required option is missing, that missing option must be written explicitly under that story.

The final consolidation must also count:
- which existing options/features were used across the stories
- which missing options were requested most often

## Preferred role split

### Role 1 — Actor / profile builder
Create likely actors and user profiles such as:
- end customers
- premium customers
- rushed customers
- confused customers
- loyal returning customers
- dishonest or abusive customers
- elderly users
- parents with children if relevant
- internal owner / manager
- staff / operators
- partners / subcontractors if relevant

### Role 2 — Situation / behavior mapper
Create likely situations and states such as:
- best case
- normal case
- rushed case
- inattentive case
- stressed case
- aggressive case
- dishonest case
- misunderstanding
- delay
- no-show
- conflict
- overload
- outage / exception if relevant

### Role 3 — Client-facing story writer
Write end-to-end stories involving:
- discovery
- request / booking / ordering
- interaction
- issue handling
- follow-up
- completion

### Role 4 — Internal / operational story writer
Write stories involving:
- owner
- manager
- staff
- operators
- dispatch / coordination
- internal validation
- conflict handling
- overload and exceptions

### Role 5 — Consolidator
Merge everything into a final structured scenario map.
Group by logic and highlight patterns.
Do not over-compress.

## Mandatory workflow

### Step 1 — Re-read all upstream artifacts
Restate briefly:
- what the client does
- what matters in the market context
- what business ideas were identified
- what technical ideas / features were identified

### Step 2 — Build the actor catalog
Generate a broad actor list.
Include both external and internal actors.
Include normal and difficult profiles.
The actor catalog should be large enough to create meaningful variation, not just 3 or 4 generic profiles.

### Step 3 — Build the situation catalog
Generate a broad situation list.
Include:
- normal situations
- exceptional situations
- conflict situations
- dishonest behavior if relevant
- stress / urgency situations
- operational failures if relevant

From bmoby/team-hermes-skills, MIT.

More from bmoby/team-hermes-skills