SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillspm-journey

pm-journey

Data & analytics

View repository

Updated 10-15 23:47

About this skill

Preamble (run first)

# 检查是否有需求调研报告
if [ ! -f "docs/01-需求调研/需求调研报告.md" ]; then
  echo "⚠️  未找到需求调研报告"
  echo ""
  echo "建议先执行 /pm-demand 了解用户信息"
  echo ""
  echo "您可以选择："
  echo "A) 执行 /pm-demand 先了解用户信息（推荐）"
  echo "B) 手动输入用户信息（快速模式）"
fi

Boundaries when writing

Do not write files when only discussing, and do not create directories during startup checks. When the user requests to save artifacts, first confirm the current product, the exact output path, and the overwrite/append choice for existing files; after confirmationonly before the actual Writecreate the parent directory of that output file. For complete installation, see skills/_shared/artifact-policy.md, and installing this skill separately also follows this section.

Cross-Agent interaction rules

When the flow requires interaction with the user:

  1. If the current environment supports AskUserQuestion, use AskUserQuestion (best experience).
  2. If the current environment does not support AskUserQuestion, you must ask the same question using a normal chat message.
  3. Ask only one question at a time.
  4. After asking, you must stop the current turn and wait for the user's answer (STOP and WAIT).
  5. Do not generate documents or write to docs before the user answers.
  6. Existing docs files cannot replace the user's answer in this round.

Execution flow

Step 1: Read prerequisite data

Use the Read tool to read:

  • docs/01-需求调研/需求调研报告.md(extract target users)
  • docs/01-需求调研/MVP方案.md(extract core functions, if any)

Step 2: Determine the user type

Use AskUserQuestion:

🎯 Which type of user's journey should be mapped?

A) New users - users using the product for the first time B) Active users - users who frequently use the product C) Churned users - users who were once active but have stopped using it D) Paying users - users who have paid E) Other (please enter manually)

Step 3: Determine the journey scenario

What task does the user want to complete?

A) Core task - the product's main function (such as purchasing or placing an order) B) Onboarding task - the new user guidance flow C) Exploration task - discovering new features D) Problem solving - seeking help or solving a problem E) Other (please enter manually)

Step 4: Map the user journey

AI guides the user to break down the journey stages:

Question 1: Journey stages

What stages does the user go through to complete the task?

For example: "Discover product → Register → First use → Deep use → Refer and share"

Please enter each stage (one stage per line):

After the user enters them, record to the list JOURNEY_STAGES

Question 2: Detailed analysis of each stage

For each stage, the AI asks:

Stage: {stage name}

Question 2.1: User behavior

In the "{stage name}" stage, what specifically does the user do?

For example: "search keywords", "browse the product list", "compare prices"

Please describe the user behavior:

Question 2.2: Touchpoints

Through what channel/entry point does the user enter this stage?

A) Mobile app B) Web C) Mini program D) Third-party platform E) Other (please enter manually)

Question 2.3: User emotions

At this stage, how does the user feel?

A) Anticipation and excitement 😊 B) Calm and focused 😐 C) Confused and anxious 😕 D) Frustrated and dissatisfied 😠 E) Satisfied and pleased 😄

Record to the variable USER_EMOTION

Question 2.4: Pain points

At this stage, what problems might users encounter?

A) Complex operation - too many steps B) Unclear information - don't know what to do C) Waiting time too long D) Missing functionality E) No obvious pain points

If the user selects a specific pain point, ask:

How severe is this pain point?

A) Mild - users can tolerate it B) Moderate - affects the experience C) Severe - may lead to user churn

Question 2.5: Opportunity points

For the pain points at this stage, what improvement opportunities are there?

Please describe your ideas:

Step 5: Draw the emotion curve

AI draws the emotion curve based on user input:

情绪值
  5 |        😄
  4 |   😊              😄
  3 |        😐
  2 |             😕
  1 |                  😠
  0 +------------------------
     发   注   首   深   推
     现   册   次   度   荐
          使   使   分
          用   用   享

Step 6: Generate the user journey map

Use the Write tool to create docs/01-需求调研/用户旅程地图.md：

# 用户旅程地图

## 一、用户画像

- **用户类型**: {用户类型}
- **任务场景**: {任务场景}
- **生成时间**: {当前时间}

---

## 二、旅程概览

Stage: {Stage 1} → {Stage 2} → {Stage 3} → {Stage 4} → {Stage 5}


---

## 三、详细旅程分析

### 阶段 1: {阶段名称}

**用户行为**:
- {行为1}
- {行为2}

**触点**:
- {触点1}
- {触点2}

**用户情绪**: {情绪} {emoji}

**痛点**:
- {痛点1}（严重程度：{程度}）
- {痛点2}

**机会点**:
- {机会1}
- {机会2}

---

### 阶段 2: {阶段名称}

**用户行为**:
- {行为1}

**触点**:
- {触点1}

**用户情绪**: {情绪} {emoji}

**痛点**:
- {痛点1}

**机会点**:
- {机会1}

---

## 四、情绪曲线

Emotion value 5 | 😄 4 | 😊 😄 3 | 😐 2 | 😕 1 | 😠 0 +------------------------ {Stage 1} {Stage 2} {Stage 3} {Stage 4} {Stage 5}


---

## 五、痛点汇总

| 阶段 | 痛点 | 严重程度 | 影响 |
|------|------|----------|------|
| {阶段1} | {痛点} | {程度} | {影响} |
| {阶段2} | {痛点} | {程度} | {影响} |

---

## 六、机会点汇总

| 阶段 | 机会点 | 预期效果 | 优先级 |
|------|--------|----------|--------|
| {阶段1} | {机会} | {效果} | P0 |
| {阶段2} | {机会} | {效果} | P1 |

---

## 七、改进建议

### 7.1 短期优化（1-2周）

1. {建议1}
2. {建议2}

### 7.2 中期优化（1-2月）

1. {建议1}
2. {建议2}

### 7.3 长期规划（3-6月）

1. {建议1}

---

## 八、下一步建议

建议执行：

1. **/pm-docs** - 生成PRD文档（推荐）
2. **/pm-proto** - 原型设计
3. **/pm-priority** - 对改进机会排序

---

**项目状态**: 用户旅程地图完成
**生成时间**: {时间戳}
**生成工具**: super-pm

Step 7: Output completion prompt

Use AskUserQuestion:

✅ User journey map complete!

📄 User journey map has been generated:docs/01-需求调研/用户旅程地图.md

🎯 Suggested next steps:

A) Run /pm-docs - Generate PRD document (recommended) B) Run /pm-proto - Prototype design C) Run /pm-priority - Prioritize improvement opportunities D) View the user journey map

Fallback mechanism

Scenario 1: No requirement data

Provide a quick mode to manually enter user information.

Scenario 2: Too many stages

If stages > 7, remind the user to simplify:

⚠️ There are many stages ({N}), it is recommended to focus on the core stages

You can choose: A) Keep all stages B) Analyze only the core stages

Notes

  1. User perspective: Always describe behavior and emotions from the user's perspective
  2. Specific pain points: Avoid speaking in generalities; be specific and actionable
  3. Emotion curve: Intuitively show changes in the user experience
  4. Actionable opportunities: Improvement suggestions must be executable
  5. Markdown storage: The journey map is human-readable and editable

Output quality comparison

✅ Good example：

- 有数据引用：「根据 Q4 数据，留存率从 35% 降至 28%」
- 有验证来源：「数据来源：Google Analytics, 2025-12-01」
- 有明确建议：「建议将新手引导步骤从 5 步减少至 3 步」

❌ Bad example：

- 模糊结论：「数据表明留存率有所下降」
- 无来源：「根据经验，这个功能很重要」
- 没有行动建议：「留存是个问题」

Common pitfalls / Red Flags — STOP

Stop immediately and backtrack if any of the following occur:

Pitfall Correct approach
Using "should", "probably", "seems" to draw conclusions Must be based on actual data and verification
Claiming completion without running checks Verify first, then state
Skipping key steps due to time pressure No exceptions; the tighter the time, the stricter you must be
The thought "it should be fine this time" Re-verify every time

Output quality check / Verification Checklist

  • Prerequisite dependencies are satisfied (input documents/data have been collected)
  • All core steps have been executed
  • Output document has been generated to the docs/ directory
  • Every judgment is supported by data/evidence
  • Recommended 2-3 follow-up skills

⚠️ If any item is not passed → complete it before marking as done.