user-story-mapping by deanpeters/product-manager-skills
npx skills add https://github.com/deanpeters/product-manager-skills --skill user-story-mapping通过创建层次化地图来可视化用户旅程,将高级活动分解为步骤和任务,并按照从左到右的叙事流进行组织。使用此方法来建立产品、设计和工程团队之间的共同理解,基于用户工作流确定功能优先级,并识别用户体验中的差距或机会。
这不是待办事项清单——它是一种战略产物,展示了用户_如何_实现其目标,从而指导_要构建什么_。
由 Jeff Patton 发明,故事地图将工作组织成二维结构:
水平轴(从左到右): 随时间推移的用户旅程
垂直轴(从上到下): 优先级和发布
Segment → Persona → Narrative (User's goal)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]
↓ ↓ ↓ ↓ ↓
[Step 1.1] [Step 2.1] [Step 3.1] [Step 4.1] [Step 5.1]
[Step 1.2] [Step 2.2] [Step 3.2] [Step 4.2] [Step 5.2]
[Step 1.3] [Step 2.3] [Step 3.3] [Step 4.3] [Step 5.3]
↓ ↓ ↓ ↓ ↓
[Task 1.1.1] [Task 2.1.1] [Task 3.1.1] [Task 4.1.1] [Task 5.1.1]
[Task 1.1.2] [Task 2.1.2] [Task 3.1.2] [Task 4.1.2] [Task 5.1.2]
[Task 1.1.3] [Task 2.1.3] [Task 3.1.3] [Task 4.1.3] [Task 5.1.3]
... ... ... ... ...
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
使用 template.md 获取完整的填充结构。
你为谁构建?
### Segment:
- [指定目标细分市场,例如:"使用 DIY 会计软件的小企业主"]
质量检查:
提供此细分市场中用户画像的详细信息(参考 skills/proto-persona/SKILL.md)。
### Persona:
- [描述用户画像:人口统计、行为、痛点、目标]
示例:
用户试图完成什么?将其框定为"待完成工作"陈述(参考 skills/jobs-to-be-done/SKILL.md)。
### Narrative:
- [用户画像目标的简明叙述,例如:"完成一个客户项目,从启动到最终付款"]
质量检查:
列出用户画像为实现叙事而参与的 3-5 个高级活动。这些构成了地图的主干。
### Activities:
1. [Activity 1, e.g., "Negotiate project scope and pricing"]
2. [Activity 2, e.g., "Execute design work"]
3. [Activity 3, e.g., "Deliver final assets to client"]
4. [Activity 4, e.g., "Send invoice and receive payment"]
5. [Activity 5, optional]
质量检查:
为每个活动列出 3-5 个详细说明活动如何执行的步骤。
### Steps:
**For Activity 1: [Activity Name]**
- Step 1: [Detail step 1, e.g., "Review client brief"]
- Step 2: [Detail step 2, e.g., "Draft project proposal"]
- Step 3: [Detail step 3, e.g., "Negotiate timeline and budget"]
- Step 4: [Optional step 4]
- Step 5: [Optional step 5]
**For Activity 2: [Activity Name]**
- Step 1: [Detail step 1]
- Step 2: [Detail step 2]
...
质量检查:
为每个步骤列出必须完成的 5-7 个任务。
### Tasks:
**For Activity 1, Step 1: [Step Name]**
- Task 1: [Detail task 1, e.g., "Read client brief document"]
- Task 2: [Detail task 2, e.g., "Identify key deliverables"]
- Task 3: [Detail task 3, e.g., "Note budget constraints"]
- Task 4: [Detail task 4, e.g., "Clarify timeline expectations"]
- Task 5: [Detail task 5, e.g., "List open questions for client"]
- Task 6: [Optional task 6]
- Task 7: [Optional task 7]
**For Activity 1, Step 2: [Step Name]**
- Task 1: [Detail task 1]
...
质量检查:
按优先级从上到下排列任务:
绘制水平的"发布线"来划分范围。
审查地图并提出问题:
查看 examples/sample.md 获取完整的故事地图示例。
症状: "活动 1:使用仪表板。活动 2:生成报告。"
后果: 你映射的是产品,而不是用户旅程。
解决方法: 重新定义为用户行动:"活动 1:监控项目进度。活动 2:为利益相关者总结工作。"
症状: 主干上有 10 个以上的活动
后果: 地图变得令人不知所措且失去焦点。
解决方法: 合并。如果你有 10 个活动,你可能混淆了活动和步骤。目标是 3-5 个高级活动。
症状: "任务 1:做这件事"
后果: 无法确定模糊任务的优先级或估算。
解决方法: 要具体:"任务 1:在'账单接收人'字段中输入客户电子邮件地址。"
症状: 所有任务处于同一级别——未定义 MVP 与未来发布
后果: 不清楚首先要构建什么。
解决方法: 明确确定优先级。绘制发布线。强制对 MVP 内容做出艰难选择。
症状: 产品经理独自创建地图,然后向团队展示
后果: 没有共同所有权或理解。
解决方法: 协作映射。与产品、设计和工程团队一起举办故事地图研讨会。
skills/proto-persona/SKILL.md — 定义故事地图的用户画像skills/jobs-to-be-done/SKILL.md — 为叙事和活动提供信息skills/user-story/SKILL.md — 地图中的任务变为用户故事skills/problem-statement/SKILL.md — 问题陈述框定叙事https://github.com/deanpeters/product-manager-prompts 仓库中的 prompts/user-story-mapping.md。Skill type: Component Suggested filename: user-story-mapping.md Suggested placement: /skills/components/ Dependencies: References skills/proto-persona/SKILL.md, skills/jobs-to-be-done/SKILL.md, skills/user-story/SKILL.md, skills/problem-statement/SKILL.md
Weekly Installs
255
Repository
GitHub Stars
1.5K
First Seen
Feb 12, 2026
Security Audits
Installed on
codex226
opencode223
gemini-cli219
github-copilot218
cursor217
kimi-cli215
Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.
This is not a backlog—it's a strategic artifact that shows how users accomplish their goals, which then informs what to build.
Invented by Jeff Patton, story mapping organizes work into a 2D structure:
Horizontal axis (left-to-right): User journey over time
Vertical axis (top-to-bottom): Priority and releases
Segment → Persona → Narrative (User's goal)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]
↓ ↓ ↓ ↓ ↓
[Step 1.1] [Step 2.1] [Step 3.1] [Step 4.1] [Step 5.1]
[Step 1.2] [Step 2.2] [Step 3.2] [Step 4.2] [Step 5.2]
[Step 1.3] [Step 2.3] [Step 3.3] [Step 4.3] [Step 5.3]
↓ ↓ ↓ ↓ ↓
[Task 1.1.1] [Task 2.1.1] [Task 3.1.1] [Task 4.1.1] [Task 5.1.1]
[Task 1.1.2] [Task 2.1.2] [Task 3.1.2] [Task 4.1.2] [Task 5.1.2]
[Task 1.1.3] [Task 2.1.3] [Task 3.1.3] [Task 4.1.3] [Task 5.1.3]
... ... ... ... ...
Use template.md for the full fill-in structure.
Who are you building for?
### Segment:
- [Specify the target segment, e.g., "Small business owners using DIY accounting software"]
Quality checks:
Provide details about the persona within this segment (reference skills/proto-persona/SKILL.md).
### Persona:
- [Describe the persona: demographics, behaviors, pains, goals]
Example:
What is the user trying to accomplish? Frame this as a Jobs-to-be-Done statement (reference skills/jobs-to-be-done/SKILL.md).
### Narrative:
- [Concise narrative of the persona's objective, e.g., "Complete a client project from kickoff to final payment"]
Quality checks:
List 3-5 high-level activities the persona engages in to fulfill the narrative. These form the backbone of your map.
### Activities:
1. [Activity 1, e.g., "Negotiate project scope and pricing"]
2. [Activity 2, e.g., "Execute design work"]
3. [Activity 3, e.g., "Deliver final assets to client"]
4. [Activity 4, e.g., "Send invoice and receive payment"]
5. [Activity 5, optional]
Quality checks:
For each activity, list 3-5 steps that detail how the activity is carried out.
### Steps:
**For Activity 1: [Activity Name]**
- Step 1: [Detail step 1, e.g., "Review client brief"]
- Step 2: [Detail step 2, e.g., "Draft project proposal"]
- Step 3: [Detail step 3, e.g., "Negotiate timeline and budget"]
- Step 4: [Optional step 4]
- Step 5: [Optional step 5]
**For Activity 2: [Activity Name]**
- Step 1: [Detail step 1]
- Step 2: [Detail step 2]
...
Quality checks:
For each step, list 5-7 tasks that must be completed.
### Tasks:
**For Activity 1, Step 1: [Step Name]**
- Task 1: [Detail task 1, e.g., "Read client brief document"]
- Task 2: [Detail task 2, e.g., "Identify key deliverables"]
- Task 3: [Detail task 3, e.g., "Note budget constraints"]
- Task 4: [Detail task 4, e.g., "Clarify timeline expectations"]
- Task 5: [Detail task 5, e.g., "List open questions for client"]
- Task 6: [Optional task 6]
- Task 7: [Optional task 7]
**For Activity 1, Step 2: [Step Name]**
- Task 1: [Detail task 1]
...
Quality checks:
Arrange tasks top-to-bottom by priority:
Draw horizontal "release lines" to demarcate scope.
Review the map and ask:
See examples/sample.md for a full story map example.
Symptom: "Activity 1: Use the dashboard. Activity 2: Generate reports."
Consequence: You've mapped the product, not the user journey.
Fix: Reframe as user actions: "Activity 1: Monitor project progress. Activity 2: Summarize work for stakeholders."
Symptom: 10+ activities across the backbone
Consequence: Map becomes overwhelming and loses focus.
Fix: Consolidate. If you have 10 activities, you're likely mixing activities with steps. Aim for 3-5 high-level activities.
Symptom: "Task 1: Do the thing"
Consequence: Can't prioritize or estimate vague tasks.
Fix: Be specific: "Task 1: Enter client email address in the 'Bill To' field."
Symptom: All tasks at the same level—no MVP vs. future releases defined
Consequence: No clarity on what to build first.
Fix: Explicitly prioritize. Draw release lines. Force hard choices about what's MVP.
Symptom: PM creates the map alone, then presents it to the team
Consequence: No shared ownership or understanding.
Fix: Map collaboratively. Run a story mapping workshop with product, design, and engineering.
skills/proto-persona/SKILL.md — Defines the persona for the story mapskills/jobs-to-be-done/SKILL.md — Informs the narrative and activitiesskills/user-story/SKILL.md — Tasks from the map become user storiesskills/problem-statement/SKILL.md — Problem statement frames the narrativeprompts/user-story-mapping.md in the https://github.com/deanpeters/product-manager-prompts repo.Skill type: Component Suggested filename: user-story-mapping.md Suggested placement: /skills/components/ Dependencies: References skills/proto-persona/SKILL.md, skills/jobs-to-be-done/SKILL.md, skills/user-story/SKILL.md, skills/problem-statement/SKILL.md
Weekly Installs
255
Repository
GitHub Stars
1.5K
First Seen
Feb 12, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex226
opencode223
gemini-cli219
github-copilot218
cursor217
kimi-cli215
推荐与联盟计划设计优化指南:病毒式增长营销策略、客户推荐计划、联盟营销
26,100 周安装