Packs
3 packscurated
Customer Journey Mapping
Map the end-to-end customer journey, identify friction points, and uncover improvement opportunities.
5 skills · pack
curated
Customer Journey Map
Install this pack to create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.
4 skills · pack
@owl-listener
Design Research
User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, and card sorting.
12 skills · pack
Results for “journey-map”
7 skillsMore results
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
1
wayfinder
Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.
580 · bundle
onboard-context-matic
Guides users through an interactive tour of the context-matic MCP server, explaining its purpose and demonstrating all available APIs with live tool calls.
36.2k
user-flow-modeling
`analysis-agent`/`task-agent`: use when actor journeys change entries, branches, interruption, recovery, authority, or side effects; skip route/state-only work.
4 · bundle
whiteboard
Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.
0 · bundle
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
3 · bundle