product-journey

Generates a product journey document mapping user stages, touchpoints, emotions, and slice signals.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-journey-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-journey
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/product-journey
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill product-journey-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often lack a structured view of the full user experience, making it hard to identify pain points, critical decision moments, and what the system must support at each stage. This Skill interviews the user and produces a standardized Product Journey document that downstream Scrum planning skills can consume. ## Core Features & Use Cases - Structured Journey Interview: Guides a one-question-at-a-time interview covering stages, goals, actions, touchpoints, emotions, pain points, and opportunities. - Slice Signal Extraction: Captures plain-language system requirements per stage with stable Stage IDs (S-1, S-2) that the slices-discovery skill uses to plan scope. - Context Reuse: Reads the existing PRD and personas documents to avoid re-asking documented information and merges PRD slice signals into the relevant journey stages. - Use Case: After writing a PRD and personas for a new app, run this Skill to map the journey from discovery to retention, producing docs/01_product/05_product_journey.md ready for backlog planning. ## Quick Start Ask the assistant to create the product journey document for your project based on the existing PRD and personas.

Frequently Asked Questions about product-journey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a user journey map for a product?▼

Run the product-journey skill, which interviews you one question at a time about each journey stage: goals, actions, touchpoints, emotions, pain points, and opportunities. It then writes a structured document to docs/01_product/05_product_journey.md.

What inputs does the product journey skill need?▼

It reads docs/01_product/01_prd.md and docs/01_product/04_personas.md if they exist, extracting the primary user, core problem, and any PRD slice signals. Missing documents are fine; the interview gathers the needed context directly.

What are slice signals in a product journey document?▼

Slice signals are plain-language statements of what the system must support at each stage, free of technical decisions like databases or APIs. The slices-discovery skill uses them, along with Stage IDs and entity lists, to plan scope and data questions.

Can I define my own journey stages instead of a template?▼

Yes. The first interview question asks you to name your own stages in order, from first contact to regular use. The skill does not impose a fixed template and adapts all follow-up questions to the stages you define.

Where is the product journey document saved?▼

The document is written to docs/01_product/05_product_journey.md. The skill first detects the docs folder with a find command, asks which one to use if multiple exist, and creates the folder if it is missing.