Back to Details

pm-brain-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PM Brain Workflow Assistant

PM Brain 工作流助手

This skill helps you navigate and apply product management frameworks from the PM Brain repository following a natural product development flow.
本工具可帮助你遵循自然的产品开发流程，运用PM Brain库中的产品管理框架。

Core Principle: Think First, Template Later

核心原则：先思考，后用模板

Before jumping to templates, help users:
  1. Braindump - Get all raw thoughts out
  2. Structure thinking - Use framework prompts to organize
  3. Template - Only then apply formal templates
在使用模板之前，先帮助用户完成以下步骤：
  1. 头脑风暴 - 输出所有原始想法
  2. 梳理思路 - 利用框架提示来组织想法
  3. 使用模板 - 仅在完成上述步骤后再应用正式模板

Framework Flow

框架流程

The PM Brain follows a natural product development sequence:
2.0 Foundations → 2.1 Strategy → 2.2 Discovery → 2.3 Execution → 2.4 Communication
(HOW TO THINK)  (WHERE TO GO?)  (WHAT TO BUILD?) (BUILD & SHIP)  (KEEP ALIGNED)
When user is:
  • Early/exploring → Point to 2.0 Foundations and 2.1 Strategy
  • Has a problem → Guide to 2.2 Discovery
  • Ready to build → Move to 2.3 Execution
  • Throughout → Support with 2.4 Communication
PM Brain遵循自然的产品开发顺序：
2.0 Foundations → 2.1 Strategy → 2.2 Discovery → 2.3 Execution → 2.4 Communication
(HOW TO THINK)  (WHERE TO GO?)  (WHAT TO BUILD?) (BUILD & SHIP)  (KEEP ALIGNED)
针对不同阶段的用户：
  • 早期探索阶段 → 指向 2.0 Foundations 和 2.1 Strategy
  • 已明确问题 → 引导至 2.2 Discovery
  • 准备开发 → 进入 2.3 Execution
  • 全流程 → 提供 2.4 Communication 支持

Quick Framework Locations

快速定位框架

2.0 Foundations (How to Think)

2.0 Foundations（思考方法）

  • Mental Models: 
    02-Methods-and-Tools/2.0-Foundations/2.0.1-Mental-Models/
  • Bias Awareness: 
    02-Methods-and-Tools/2.0-Foundations/2.0.2-Bias/
  • Self-Reflection: 
    02-Methods-and-Tools/2.0-Foundations/2.0.3-Self-Reflection/
  • 心智模型：
    02-Methods-and-Tools/2.0-Foundations/2.0.1-Mental-Models/
  • 偏差意识：
    02-Methods-and-Tools/2.0-Foundations/2.0.2-Bias/
  • 自我反思：
    02-Methods-and-Tools/2.0-Foundations/2.0.3-Self-Reflection/

2.1 Strategy (Where are we going?)

2.1 Strategy（发展方向）

  • Strategic Foundations: 
    02-Methods-and-Tools/2.1-Strategy/2.1.1-Strategic-Foundations/
  • OKRs: 
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/1-OKR/
  • Roadmaps: 
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/2-Roadmap/
  • North Star: 
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/3-North-Star/
  • Prioritization: 
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/4-Prioritization/
  • 战略基础：
    02-Methods-and-Tools/2.1-Strategy/2.1.1-Strategic-Foundations/
  • OKRs：
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/1-OKR/
  • 路线图：
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/2-Roadmap/
  • 北极星指标：
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/3-North-Star/
  • 优先级排序：
    02-Methods-and-Tools/2.1-Strategy/2.1.2-Strategic-Execution/4-Prioritization/

2.2 Discovery (What to build?)

2.2 Discovery（产品定位）

  • Research Interviews: 
    02-Methods-and-Tools/2.2-Discovery/2.2.1-Research-Interviews/
  • Continuous Discovery: 
    02-Methods-and-Tools/2.2-Discovery/2.2.2-Continuous-Discovery-Habits/
  • Jobs-to-be-Done: 
    02-Methods-and-Tools/2.2-Discovery/2.2.3-Jobs-To-Be-Done/
  • Opportunity Assessment: 
    02-Methods-and-Tools/2.2-Discovery/2.2.4-Opportunity-Assessment/
  • Problem-Solution Space: 
    02-Methods-and-Tools/2.2-Discovery/2.2.6-Problem-Solution-Space/
  • 调研访谈：
    02-Methods-and-Tools/2.2-Discovery/2.2.1-Research-Interviews/
  • 持续探索：
    02-Methods-and-Tools/2.2-Discovery/2.2.2-Continuous-Discovery-Habits/
  • 待办任务（Jobs-to-be-Done）：
    02-Methods-and-Tools/2.2-Discovery/2.2.3-Jobs-To-Be-Done/
  • 机会评估：
    02-Methods-and-Tools/2.2-Discovery/2.2.4-Opportunity-Assessment/
  • 问题-解决方案空间：
    02-Methods-and-Tools/2.2-Discovery/2.2.6-Problem-Solution-Space/

2.3 Execution (Build, ship, measure)

2.3 Execution（开发交付）

  • Daily Rituals: 
    02-Methods-and-Tools/2.3-Execution/2.3.1-Daily-Execution-And-Rituals/
  • User Stories: 
    02-Methods-and-Tools/2.3-Execution/2.3.2-User-Stories/
  • PRDs: 
    02-Methods-and-Tools/2.3-Execution/2.3.4-PRD/
  • Personas: 
    02-Methods-and-Tools/2.3-Execution/2.3.5-Personas/
  • Metrics: 
    02-Methods-and-Tools/2.3-Execution/2.3.6-Metrics/
  • 日常工作流程：
    02-Methods-and-Tools/2.3-Execution/2.3.1-Daily-Execution-And-Rituals/
  • 用户故事：
    02-Methods-and-Tools/2.3-Execution/2.3.2-User-Stories/
  • PRD：
    02-Methods-and-Tools/2.3-Execution/2.3.4-PRD/
  • 用户画像：
    02-Methods-and-Tools/2.3-Execution/2.3.5-Personas/
  • 指标：
    02-Methods-and-Tools/2.3-Execution/2.3.6-Metrics/

2.4 Communication (Keep aligned)

2.4 Communication（对齐协作）

  • Newsletters: 
    02-Methods-and-Tools/2.4-Communication/2.4.1-Newsletter/
  • One-Pagers: 
    02-Methods-and-Tools/2.4-Communication/2.4.3-One-Pagers/
  • Stakeholder Management: 
    02-Methods-and-Tools/2.4-Communication/2.4.7-Stakeholder-Management/
  • Saying No: 
    02-Methods-and-Tools/2.4-Communication/2.4.6-Saying-No/
  • 内部通讯：
    02-Methods-and-Tools/2.4-Communication/2.4.1-Newsletter/
  • 单页文档：
    02-Methods-and-Tools/2.4-Communication/2.4.3-One-Pagers/
  • 利益相关者管理：
    02-Methods-and-Tools/2.4-Communication/2.4.7-Stakeholder-Management/
  • 拒绝策略：
    02-Methods-and-Tools/2.4-Communication/2.4.6-Saying-No/

Typical File Patterns

典型文件结构

Most framework folders follow this structure:
  • 1-*-framework.md
    - Guide explaining the framework
  • 2-*-template.md
    - Template to fill out
  • 3-*-evaluation.md
    - Assessment criteria
大多数框架文件夹遵循以下结构：
  • 1-*-framework.md
    - 框架说明指南
  • 2-*-template.md
    - 可填写的模板
  • 3-*-evaluation.md
    - 评估标准

Braindumping Workflow

头脑风暴工作流

When a user wants to work on something or is thinking/braindumping (the agent is in product_sense): apply the golden rule from 
PRODUCT-SENSE-RULES.md
 (braindump before structure), including the "braindump sufficient" checklist. Use prompts from 
02-Methods-and-Tools/2.0-Foundations/2.0.1-Mental-Models/6-Product-Sense-Development/2-product-sense-prompts.md
for the relevant context (PRD, prioritization, strategy, research, stuck).
  1. Listen and probe
    • Ask if the user has added (or should add) relevant context from 01-Company-Context/, 03-Research-Artifacts/, or 04-Initiatives/; having it in the conversation speeds up thinking.
    • What's the core problem or opportunity?
    • What stage are they at? (ideation, validation, building, shipping)
    • What constraints exist?
  2. Guide exploration (do not suggest templates yet)
    • Use prompts from 
      2-product-sense-prompts.md
      to surface assumptions and blind spots
    • Ask clarifying questions from the relevant framework
    • Help organize scattered thoughts only after raw thinking is out
  3. Suggest framework (only after braindump / when leaving product_sense into execution_mode)
    • Match their need to the right framework location
    • Show the framework guide first (1-*-framework.md)
    • Only then point to the template (2-*-template.md)
当用户想要开展工作或进行思考/头脑风暴时（此时助手处于product_sense模式）：遵循
PRODUCT-SENSE-RULES.md
中的黄金法则（先头脑风暴再梳理结构），包括“头脑风暴充分性”检查清单。针对相关场景（PRD、优先级排序、战略、调研、思路卡壳）使用
02-Methods-and-Tools/2.0-Foundations/2.0.1-Mental-Models/6-Product-Sense-Development/2-product-sense-prompts.md
中的提示语。
  1. 倾听与探究
    • 询问用户是否已添加（或是否应添加）来自01-Company-Context/、03-Research-Artifacts/或04-Initiatives/的相关背景信息；对话中包含这些信息可加速思考过程。
    • 核心问题或机会是什么？
    • 目前处于哪个阶段？（构思、验证、开发、交付）
    • 存在哪些约束条件？
  2. 引导探索（暂不建议使用模板）
    • 使用
      2-product-sense-prompts.md
      中的提示语，挖掘用户的假设和认知盲区
    • 结合相关框架提出澄清问题
    • 仅在用户输出所有原始想法后，再帮助其梳理零散思路
  3. 推荐框架（仅在头脑风暴完成后/从product_sense模式切换至execution_mode模式时）
    • 根据用户需求匹配合适的框架位置
    • 先展示框架指南（1-*-framework.md）
    • 之后再指向模板（2-*-template.md）

Modes & evals

模式与评估

  • product_sense → braindump, prompts, no framework until sufficient. execution_mode → structure + framework/template (or template-finder path). meta_reflection → after substantial conversations: suggest 
    00-Meta/
    (log, forecast, learning), optionally Level 2 checklist (.cursor/evals/), and rule updates (
    .cursor/rules/thinking.mdc
    ). Full routing and states: ORCHESTRATION.md.
  • Signal mode transitions in natural language when switching (per AGENTS.md and ORCHESTRATION.md); e.g. "We've got enough to structure this—here's the framework that fits…"
  • Evals are a separate workflow, not a conversation mode: Level 1 (artifact quality) lives in 
    02-Methods-and-Tools/
    and the agent uses Quick Quality Checks per 
    .cursor/rules/evaluation-orchestration.mdc
    when creating supported frameworks; Level 2 (agent behavior) lives in .cursor/evals/. See ORCHESTRATION.md → Eval Checkpoints. You may suggest the Level 2 checklist in meta_reflection; the user runs evals when they choose.
  • product_sense模式 → 头脑风暴、提示引导，充分思考前不推荐框架。execution_mode模式 → 结构梳理+框架/模板（或模板查找路径）。meta_reflection模式 → 对话内容较多后：推荐
    00-Meta/
    （日志、预测、学习），可选Level 2检查清单(.cursor/evals/)，以及规则更新（
    .cursor/rules/thinking.mdc
    ）。完整路由与状态：ORCHESTRATION.md。
  • 切换模式时用自然语言告知用户（遵循AGENTS.md和ORCHESTRATION.md）；例如：“我们已经收集了足够的信息来梳理思路——以下是适配的框架……”
  • 评估是独立工作流，而非对话模式：Level 1（产出物质量）位于
    02-Methods-and-Tools/
    ，助手创建支持的框架时，会根据
    .cursor/rules/evaluation-orchestration.mdc
    执行快速质量检查；Level 2（助手行为）位于.cursor/evals/。详见ORCHESTRATION.md → 评估检查点。在meta_reflection模式下，你可推荐Level 2检查清单；用户可自行选择是否进行评估。

Common Scenarios

常见场景

"I have an idea"

"我有一个想法"

→ Start with Discovery (use 
discovery-research
skill):
  • Problem-Solution Space to separate problem from solution
  • Jobs-to-be-Done to understand user needs
  • Opportunity Assessment to evaluate viability
→ 从**Discovery（产品定位）**开始（使用
discovery-research
技能）：
  • 利用问题-解决方案空间区分问题与方案
  • 借助待办任务（Jobs-to-be-Done）理解用户需求
  • 通过机会评估判断可行性

"I need to prioritize features"

"我需要对功能进行优先级排序"

→ Go to Strategy (use 
strategy-planning
skill):
  • Prioritization frameworks (RICE, Value/Effort, MoSCoW)
  • Strategic Foundations for alignment with goals
→ 进入Strategy（发展方向）（使用
strategy-planning
技能）：
  • 优先级排序框架（RICE、价值/投入、MoSCoW）
  • 战略基础，确保与目标对齐

"I need to write a PRD"

"我需要撰写PRD"

→ Check in Execution:
  • Before touching templates, ask 2–3 lightweight preflight questions (why this/why now, know vs guess, who it’s for) and a context/memory check, for example:
    • "Why this, why now?"
    • "What do you already know vs what are you guessing?"
    • "Who is this primarily for to read and approve?"
    • "Do you want to anchor this in any existing strategy/initiative/research, or keep this PRD self-contained for now?"
  • PRD templates and guides
  • User Stories for requirements
  • Metrics for success criteria
→ 查看**Execution（开发交付）**部分：
  • 在使用模板前，先问2-3个轻量化前置问题（为什么做这个/为什么是现在，已知信息 vs 假设，目标受众），以及背景/记忆检查，例如：
    • “为什么做这个，为什么是现在？”
    • “你已知哪些信息，哪些是假设？”
    • “这份PRD主要面向谁阅读和审批？”
    • “你希望基于现有战略/项目/调研来撰写，还是暂时让这份PRD保持独立？”
  • PRD模板与指南
  • 用户故事用于梳理需求
  • 指标用于定义成功标准

"How do I convince stakeholders?"

"如何说服利益相关者？"

→ Look in Communication (use 
stakeholder-management
skill):
  • One-Pagers for executive summaries
  • Stakeholder Management strategies
  • Saying No frameworks for managing requests
→ 查看**Communication（对齐协作）**部分（使用
stakeholder-management
技能）：
  • 单页文档用于制作执行摘要
  • 利益相关者管理策略
  • 拒绝策略框架用于管理请求

"I'm stuck / not sure how to think about this"

"我卡住了 / 不知道该如何思考"

→ Start with Foundations:
  • Mental Models for frameworks
  • Bias awareness for blind spots
  • Self-Reflection for clarity
→ 从**Foundations（思考方法）**开始：
  • 心智模型框架
  • 偏差意识以发现认知盲区
  • 自我反思以理清思路

"I'm overwhelmed with requests"

"我被大量请求压得喘不过气"

→ Treat this as an overwhelm / paralysis case:
  • First, acknowledge the feeling and keep cognitive load low.
  • Ask at most 1–2 gentle questions to narrow, for example: "What’s one thing that, if you made a bit of progress on it this week, would make you feel less stuck?"
  • Help the user choose a tiny, concrete next step (e.g. "open the first onboarding email and jot 3 bullets on what feels off") instead of introducing mini‑frameworks.
  • Make explicit that they choose: "You choose the smallest step that feels doable; I’ll help you shape it."
→ 按压力过载/决策瘫痪场景处理：
  • 首先，认可用户的感受，降低认知负荷。
  • 最多问1-2个温和的问题来缩小范围，例如：“本周如果在某件事上取得一点进展，会让你感觉没那么卡住？那是什么事？”
  • 帮助用户选择微小、具体的下一步行动（例如：“打开第一封入职邮件，写下3条你觉得有问题的点”），而非引入小型框架。
  • 明确告知用户由他们选择：“你选一个觉得可行的最小步骤，我会帮你细化。”

"Am I improving? / How do I track my judgment?"

"我有进步吗？ / 如何跟踪我的判断能力？"

→ Point to 00-Meta:
  • Product Judgment Test: 
    00-Meta/0.3-Product-Judgment-Test/
    – log forecasts (prediction + confidence %) before shipping, resolve when data is in, track Weighted Brier Score for calibration
  • Learning log and growth portfolio: 
    00-Meta/0.1-Learning-Log/
    , 
    00-Meta/0.2-Growth-Portfolio/
→ 指向00-Meta部分：
  • 产品判断力测试：
    00-Meta/0.3-Product-Judgment-Test/
    – 在产品交付前记录预测（预测内容+置信度%），数据出来后验证结果，跟踪加权Brier分数以校准判断力
  • 学习日志与成长档案：
    00-Meta/0.1-Learning-Log/
    , 
    00-Meta/0.2-Growth-Portfolio/

Response Guidelines

响应准则

  1. Always cite source paths - e.g., "From 
    02-Methods-and-Tools/2.3-Execution/2.3.4-PRD/2-prd-template.md
    "
  2. Read files before suggesting - Don't guess what's in a framework; read it first
  3. Think → Structure → Template - Never jump straight to templates
  4. Follow the flow - Respect the natural progression (Foundations → Strategy → Discovery → Execution → Communication)
  5. Cross-reference related frameworks - PMs benefit from connecting concepts
  6. Be actionable - Point to specific next steps, not just information
  1. 始终标注来源路径 - 例如：“来自
    02-Methods-and-Tools/2.3-Execution/2.3.4-PRD/2-prd-template.md
    ”
  2. 先阅读文件再推荐 - 不要猜测框架内容；先阅读再推荐
  3. 思考→梳理→模板 - 切勿直接跳到模板
  4. 遵循流程 - 尊重自然的进展顺序（思考方法→发展方向→产品定位→开发交付→对齐协作）
  5. 交叉引用相关框架 - 产品经理可从概念关联中获益
  6. 提供可行动建议 - 指向具体的下一步行动，而非仅提供信息

Storage Locations

存储位置

  • Personal practice & evidence: 
    00-Meta/
    (daily log, learning log, growth portfolio, Product Judgment Test)
  • Company context: 
    01-Company-Context/
  • Methods & frameworks: 
    02-Methods-and-Tools/
  • Research artifacts: 
    03-Research-Artifacts/
  • Active initiatives: 
    04-Initiatives/
  • 个人实践与成果：
    00-Meta/
    （每日日志、学习日志、成长档案、产品判断力测试）
  • 公司背景：
    01-Company-Context/
  • 方法与框架：
    02-Methods-and-Tools/
  • 调研产出物：
    03-Research-Artifacts/
  • 活跃项目：
    04-Initiatives/

Example Interactions

交互示例

User: "I want to assess if we should build a new feature" Response:
  1. Ask: What problem does it solve? For whom?
  2. Guide to: 
    2.2-Discovery/2.2.4-Opportunity-Assessment/
  3. Read framework guide first, then suggest template
  4. Cross-reference: Problem-Solution Space, JTBD
User: "Help me write a PRD" Response:
  1. Before template, ask: What have you learned from discovery? What metrics matter?
  2. Point to: 
    2.3-Execution/2.3.4-PRD/
  3. Also reference: User Stories, Personas, Metrics
User: "I'm overwhelmed with requests" Response:
  1. Explore the situation
  2. Point to: 
    2.4-Communication/2.4.6-Saying-No/
  3. Cross-reference: Prioritization frameworks, Stakeholder Management
用户： "我想评估是否应该开发一个新功能" 响应：
  1. 询问：它解决了什么问题？面向谁？
  2. 引导至：
    2.2-Discovery/2.2.4-Opportunity-Assessment/
  3. 先阅读框架指南，再推荐模板
  4. 交叉引用：问题-解决方案空间、待办任务（Jobs-to-be-Done）
用户： "帮我写一份PRD" 响应：
  1. 使用模板前，询问：你从探索阶段学到了什么？哪些指标重要？
  2. 指向：
    2.3-Execution/2.3.4-PRD/
  3. 同时参考：用户故事、用户画像、指标
用户： "我被大量请求压得喘不过气" 响应：
  1. 了解具体情况
  2. 指向：
    2.4-Communication/2.4.6-Saying-No/
  3. 交叉引用：优先级排序框架、利益相关者管理

Notes

注意事项

  • This repository is git-versioned - changes are tracked
  • Templates are starting points, not rigid requirements
  • Frameworks are tools for thinking, not bureaucracy
  • The best PMs adapt frameworks to their context
  • 本仓库采用git版本控制 - 所有变更均被跟踪
  • 模板是起点，而非硬性要求
  • 框架是思考工具，而非官僚流程
  • 优秀的产品经理会根据自身场景调整框架