From pm-copilot
Use this skill when the user asks to "create a journey map", "user journey map", "map the user experience", "map the customer journey", "end-to-end user flow", "what does the user experience look like", "map the onboarding journey", or wants to visualize the full sequence of steps a user goes through to accomplish a goal — including touchpoints, emotions, and friction points.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
You are creating a user journey map — a visual and narrative representation of the complete user experience from awareness to outcome. Journey maps surface friction, emotion, and opportunity that individual screens or features can miss.
Framework: Service design principles, Teresa Torres (continuous discovery touchpoints), JTBD (progress map across stages).
Read memory/user-profile.md and context/product/personas.md to identify the primary persona for this journey. Understand: what product stage is the user in (pre-launch → need to map the ideal journey; existing product → need to map the current reality)?
Clarify:
Identify the major phases of the journey. Adapt to the user's specific flow, but use these as a starting point:
Awareness: How does the user first learn about the product? Consideration: What research or comparison do they do before trying it? Activation: Their first experience — signup, onboarding, first use Core loop: Regular use — the repeating pattern of value delivery Expansion: Discovering new features or use cases Retention / Renewal: Decision to continue using or subscribe Advocacy / Referral: Sharing with others
For a specific feature journey (not the full product): adapt phases to the feature's flow.
For each phase, fill in:
User actions: What does the user actually do? (Steps, clicks, inputs, decisions)
Touchpoints: Where does the user interact with the product/brand? (In-app, email, Slack, support, etc.)
Thoughts: What is the user thinking at this step? (Uncertainty, expectation, intent)
Emotions: What are they feeling? (Use a simple scale: Frustrated → Neutral → Satisfied → Delighted)
Friction points: What makes this step hard or confusing?
Opportunities: What could be improved here? What would delight them?
Metrics available: Is there data for this step? (Conversion rate, time spent, drop-off rate)
After completing the rows, draw the emotion arc:
For each friction point identified:
Rank opportunities by: severity × affected users. This gives you a data-driven prioritization of where to invest.
Produce:
Offer to save to a Notion page (if connected) or outputs/journey-map-[persona]-[goal]-[date].md.