Skill

disc-journeys

Use when mapping user journeys before requirements or solution design. Also triggers on 'journey', 'happy path', 'failure path', 'alternate flow', 'before during after', or 'anti-journey'.

From pm

Install

Run in your terminal

npx claudepluginhub etusdigital/etus-plugins --plugin pm

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

prompt-lookup

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.

prompts.chat

157.6k

skill-lookup

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.

prompts.chat

157.6k

Agent Development

6 files

Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.

plugin-dev

83.2k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Elicitation Entry Rule

BEFORE asking anything in this module:

Read elicitation-state.yaml (at docs/ets/projects/{project-slug}/state/ or knowledge/ template)

Find this module's entry in module_state

If status == "covered" → summarize what exists, ask if user wants to go deeper

If status == "in_progress" → continue from current_probe

If status == "not_started" → start with story probe (see .claude/skills/discovery/knowledge/story-probes.md)

After each question → update elicitation-state.yaml

Journey Sweep

Elicitation Entry Rule

BEFORE asking anything in this module:

Read elicitation-state.yaml (at docs/ets/projects/{project-slug}/state/ or knowledge/ template)
Find this module's entry in module_state
If status == "covered" → summarize what exists, ask if user wants to go deeper
If status == "in_progress" → continue from current_probe
If status == "not_started" → start with story probe (see .claude/skills/discovery/knowledge/story-probes.md)
After each question → update elicitation-state.yaml

PURPOSE

Map the workflow around the problem so that downstream docs don't jump straight to screens or APIs.

This skill writes journey coverage into the Opportunity Pack as JOUR-# entries and should connect each journey to actors, JTBDs, and use cases.

REQUIRED COVERAGE

For each important actor, try to cover:

before / during / after
new user / returning user / blocked user
happy path
alternate path
failure path
manual fallback or recovery path

JOURNEY FIELDS

For each JOUR-#, capture:

actor
path type
trigger
steps
moment of friction
success signal
fallback or recovery

ANTI-PATTERNS

Do not map only the ideal path
Do not confuse a journey with a UI flow
Do not skip the "before" state and trigger
Do not skip what happens after failure or partial success