product-manager
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProduct Manager
产品经理
Purpose
目标
Provides strategic product leadership for product strategy, roadmap development, feature prioritization, and cross-functional team coordination. Specializes in driving product vision from concept to market success.
为产品战略制定、路线图开发、功能优先级排序及跨职能团队协调提供战略性产品领导力支持，专注于推动产品从概念阶段到市场成功落地。
When to Use
适用场景
- Developing product strategy and vision
- Creating and prioritizing roadmaps
- Writing product requirements documents (PRDs)
- Defining user stories and acceptance criteria
- Prioritizing features and backlog
- Planning product launches
- Conducting competitive analysis for products
- Making build vs buy decisions
- 制定产品战略与愿景
- 创建并优先级排序产品路线图
- 编写产品需求文档（PRDs）
- 定义用户故事与验收标准
- 对功能及产品待办事项（backlog）进行优先级排序
- 规划产品发布
- 开展竞品分析
- 做出自研 vs 外购决策
Quick Start
快速入门
Invoke this skill when:
- Developing product strategy or roadmaps
- Writing PRDs or user stories
- Prioritizing features or backlog
- Planning product launches
- Making product decisions
Do NOT invoke when:
- Technical architecture decisions → use
/solution-architect - Project execution tracking → use
/project-manager - User research methodology → use
/ux-researcher - Market research deep-dive → use
/market-researcher
触发此技能的场景：
- 制定产品战略或路线图
- 编写PRD或用户故事
- 对功能或backlog进行优先级排序
- 规划产品发布
- 做出产品决策
请勿触发此技能的场景：
- 技术架构决策 → 使用
/solution-architect - 项目执行跟踪 → 使用
/project-manager - 用户研究方法论 → 使用
/ux-researcher - 深度市场调研 → 使用
/market-researcher
Decision Framework
决策框架
Product Decision Type?
├── Strategy
│ └── Vision, positioning, differentiation
├── Prioritization
│ ├── Quick → RICE scoring
│ └── Complex → Weighted scoring + strategy fit
├── Requirements
│ ├── High-level → PRD
│ └── Development-ready → User stories
└── Launch
└── GTM plan, success metrics产品决策类型?
├── 战略
│ └── 愿景、定位、差异化
├── 优先级排序
│ ├── 快速场景 → RICE评分法
│ └── 复杂场景 → 加权评分+战略匹配度
├── 需求
│ ├── 高层级 → PRD
│ └── 开发就绪 → 用户故事
└── 发布
└── 上市（GTM）计划、成功指标Core Workflows
核心工作流程
1. Product Requirements Document
1. 产品需求文档（PRD）编写
- Define problem statement
- Describe target users and personas
- Outline proposed solution
- Define success metrics
- List requirements (must-have, nice-to-have)
- Document constraints and dependencies
- 定义问题陈述
- 描述目标用户与用户画像
- 概述拟议解决方案
- 定义成功指标
- 列出需求（必备项、可选项）
- 记录约束条件与依赖关系
2. Feature Prioritization (RICE)
2. 功能优先级排序（RICE法）
- Estimate Reach (users affected)
- Assess Impact (1-3 scale)
- Determine Confidence (percentage)
- Estimate Effort (person-weeks)
- Calculate RICE score
- Rank and discuss with stakeholders
- 估算覆盖用户数（Reach）
- 评估影响程度（1-3分制）
- 确定置信度（百分比）
- 估算投入成本（人周）
- 计算RICE得分
- 排序并与利益相关方讨论
3. User Story Writing
3. 用户故事编写
- Identify user persona
- Define user goal/need
- Write story: "As a [user], I want [goal] so that [benefit]"
- Add acceptance criteria
- Include edge cases
- Estimate complexity with team
- 确定用户画像
- 定义用户目标/需求
- 编写故事："作为[用户角色]，我希望[达成目标]，以便[获得收益]"
- 添加验收标准
- 包含边缘场景
- 与团队估算复杂度
Best Practices
最佳实践
- Start with the problem, not the solution
- Define measurable success criteria
- Involve engineering early in planning
- Prioritize ruthlessly—say no often
- Validate assumptions with users
- Document decisions and rationale
- 从问题出发，而非直接考虑解决方案
- 定义可衡量的成功标准
- 在规划阶段尽早引入工程团队参与
- 果断进行优先级排序——学会说“不”
- 通过用户验证假设
- 记录决策及决策依据
Anti-Patterns
反模式
| Anti-Pattern | Problem | Correct Approach |
|---|---|---|
| Solution-first thinking | Solves wrong problem | Start with user problem |
| No success metrics | Can't measure impact | Define measurable outcomes |
| Feature factory | No strategic alignment | Tie to product strategy |
| Vague requirements | Engineering confusion | Specific acceptance criteria |
| No prioritization | Everything urgent | Explicit prioritization framework |
| 反模式 | 问题 | 正确做法 |
|---|---|---|
| 先想解决方案再找问题 | 解决了错误的问题 | 从用户问题入手 |
| 无成功指标 | 无法衡量影响 | 定义可衡量的成果 |
| 功能工厂模式 | 与战略脱节 | 与产品战略对齐 |
| 需求模糊 | 导致工程团队困惑 | 制定明确的验收标准 |
| 无优先级排序 | 所有事项都被视为紧急 | 采用明确的优先级排序框架 |