strategy-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Strategy & Planning Skill

战略与规划Skill

Use this skill when the user is deciding where to go and what bets to make: vision, strategy docs, OKRs, roadmaps, prioritization, and strategic tradeoffs.
当用户需要决定发展方向业务赌注时,可使用本Skill:包括愿景制定、战略文档撰写、OKRs设定、路线图规划、优先级排序以及战略取舍等场景。

When to use this skill

何时使用本Skill

Trigger this skill (usually in product_sense or execution_mode) when the user:
  • Says things like:
    • “I need to write a strategy doc”
    • “I’m planning H2 / next year”
    • “I need to create OKRs / a roadmap”
    • “I’m not sure which bets to prioritize”
    • “I’m stuck between these 2–3 big directions”
  • Or explicitly mentions:
    • Strategy, OKRs, roadmap, north star, prioritization
If their main question is discovery / research, use
discovery-research
. If it’s mainly about communication and buy-in, use
stakeholder-management
.
当用户出现以下情况时(通常处于product_sense或execution_mode模式),触发本Skill:
  • 表达类似需求:
    • “我需要撰写一份战略文档”
    • “我正在规划下半年/明年的工作”
    • “我需要制定OKRs/路线图”
    • “我不确定应该优先推进哪些业务赌注”
    • “我在2-3个重大方向之间纠结”
  • 或明确提及:
    • 战略、OKRs、路线图、北极星指标、优先级排序
如果用户的核心需求是探索/调研,请使用
discovery-research
Skill;如果核心需求是沟通与共识达成,请使用
stakeholder-management
Skill。

Relevant framework locations

相关框架位置

Most strategy frameworks live under:
  • 02-Methods-and-Tools/2.1-Strategy/
    • 2.1.1-Strategic-Foundations/
      • Strategy foundations, good-strategy/bad-strategy, Playing to Win
    • 2.1.2-Strategic-Execution/
      • 1-OKR/
        (OKRs)
      • 2-Roadmap/
        (roadmaps)
      • 3-North-Star/
        (north star metrics)
      • 4-Prioritization/
        (RICE, value/effort, MoSCoW, Kano)
大多数战略框架位于以下路径:
  • 02-Methods-and-Tools/2.1-Strategy/
    • 2.1.1-Strategic-Foundations/
      • 战略基础、好战略/坏战略、Playing to Win框架
    • 2.1.2-Strategic-Execution/
      • 1-OKR/
        (OKRs相关)
      • 2-Roadmap/
        (路线图相关)
      • 3-North-Star/
        (北极星指标)
      • 4-Prioritization/
        (RICE模型、价值/投入比、MoSCoW方法、Kano模型)

Typical flows

典型流程

1. “I need a strategy doc”

1. “我需要撰写一份战略文档”

  1. In product_sense, clarify:
    • What kind of strategy (growth, market entry, pivot, annual plan)?
    • Who is the audience (execs, peers, team)?
    • What decisions should this doc help them make?
  2. Use:
    • 2.1-Strategy/2.1.1-Strategic-Foundations/README.md
    • And, if helpful, a specific framework like:
      • 2.1.1-Strategic-Foundations/2-Good-Strategy-Bad-Strategy/1-good-strategy-bad-strategy-framework.md
      • 2.1.1-Strategic-Foundations/3-Playing-To-Win/1-playing-to-win-framework.md
  3. Transition to execution_mode:
    • Propose a structure that fits the context (e.g., context → choices → actions).
    • Pull from the user’s braindump to outline the sections.
  1. product_sense模式下,明确以下信息:
    • 战略类型(增长战略、市场进入战略、转型战略、年度规划等)?
    • 目标受众(高管、同事、团队成员)?
    • 这份文档需要辅助做出哪些决策?
  2. 参考以下内容:
    • 2.1-Strategy/2.1.1-Strategic-Foundations/README.md
    • 如有需要,可使用特定框架,例如:
      • 2.1.1-Strategic-Foundations/2-Good-Strategy-Bad-Strategy/1-good-strategy-bad-strategy-framework.md
      • 2.1.1-Strategic-Foundations/3-Playing-To-Win/1-playing-to-win-framework.md
  3. 切换至execution_mode模式:
    • 根据上下文提出合适的文档结构(例如:背景→选择→行动)。
    • 结合用户的思路梳理,完成文档大纲。

2. “Help me set OKRs”

2. “帮我制定OKRs”

  1. Clarify:
    • Timeframe and scope (team vs org, quarter vs half).
    • How OKRs will be used (alignment vs strict commitment).
  2. Point to:
    • 2.1-Strategy/2.1.2-Strategic-Execution/1-OKR/1-okr-framework.md
  3. Then:
    • In execution_mode, use
      2-okr-template.md
      to structure objectives and key results.
    • Use
      3-okr-evaluation.md
      for a quick quality check before sharing.
  1. 明确以下信息:
    • 时间范围与适用范围(团队级vs公司级,季度vs半年度)。
    • OKRs的使用场景(对齐目标vs严格承诺)。
  2. 参考:
    • 2.1-Strategy/2.1.2-Strategic-Execution/1-OKR/1-okr-framework.md
  3. 后续步骤:
    • execution_mode模式下,使用
      2-okr-template.md
      来构建目标与关键结果。
    • 在分享前,使用
      3-okr-evaluation.md
      进行快速质量检查。

3. “I need a roadmap”

3. “我需要一份路线图”

  1. Clarify:
    • Purpose (alignment vs commitment vs exploration).
    • Audience (execs, team, cross-functional partners).
  2. Point to:
    • 2.1-Strategy/2.1.2-Strategic-Execution/2-Roadmap/1-roadmap-framework.md
  3. Help choose:
    • A simple starting format (now/next/later, or quarters with themes).
    • Then use
      2-roadmap-template.md
      and
      3-roadmap-evaluation.md
      as needed.
  1. 明确以下信息:
    • 路线图的用途(对齐目标vs承诺执行vs探索方向)。
    • 目标受众(高管、团队成员、跨职能合作伙伴)。
  2. 参考:
    • 2.1-Strategy/2.1.2-Strategic-Execution/2-Roadmap/1-roadmap-framework.md
  3. 协助选择:
    • 简单的初始格式(现在/下一步/未来,或按季度划分并设置主题)。
    • 必要时使用
      2-roadmap-template.md
      3-roadmap-evaluation.md

4. “I need to prioritize features / bets”

4. “我需要对功能/业务赌注进行优先级排序”

  1. Explore:
    • What constraints matter most (capacity, risk, revenue, learning)?
    • Whether they need a lightweight or more rigorous approach.
  2. Use:
    • 2.1-Strategy/2.1.2-Strategic-Execution/4-Prioritization/decision-tree.md
      to pick an approach.
    • RICE, value/effort, MoSCoW, or Kano from that folder as appropriate.
  1. 明确以下信息:
    • 最关键的约束条件(产能、风险、收入、学习价值)?
    • 需要轻量级还是更严谨的评估方法?
  2. 使用:
    • 2.1-Strategy/2.1.2-Strategic-Execution/4-Prioritization/decision-tree.md
      来选择合适的方法。
    • 根据情况选用该文件夹中的RICE模型、价值/投入比、MoSCoW方法或Kano模型。

Response guidelines

响应准则

  1. Stay in product_sense until the problem is clear
    • Ask about goals, audience, decisions, and constraints before suggesting frameworks.
  2. Match framework to situation
    • Use
      when-to-use-which.md
      in Strategic Foundations where helpful.
  3. Anchor to company context
    • When relevant, wake:
      • 01-Company-Context/2-company-strategy.md
      • 01-Company-Context/5-company-roadmap.md
    • So strategy artifacts align with existing direction.
  4. Be explicit about tradeoffs
    • When comparing options, help them define decision criteria, not just pick a framework.
  1. 在问题明确前,保持product_sense模式
    • 在推荐框架前,先询问目标、受众、决策需求及约束条件。
  2. 匹配框架与场景
    • 必要时可参考战略基础文件夹中的
      when-to-use-which.md
      文档。
  3. 结合公司上下文
    • 相关情况下,调用以下文档:
      • 01-Company-Context/2-company-strategy.md
      • 01-Company-Context/5-company-roadmap.md
    • 确保战略产出与公司现有方向保持一致。
  4. 明确说明取舍关系
    • 对比选项时,协助用户定义决策标准,而非仅推荐框架。

Relation to other skills

与其他Skill的关系

  • pm-brain-workflow
    decides where in the Foundations → Strategy → Discovery → Execution → Communication flow you are.
  • strategy-planning
    deepens the Strategy slice: strategy docs, OKRs, roadmaps, prioritization.
  • Use
    discovery-research
    when the main need is learning and evidence.
  • Use
    stakeholder-management
    when the main need is alignment and communication.
  • pm-brain-workflow
    用于确定你处于“基础→战略→探索→执行→沟通”流程中的哪个阶段。
  • strategy-planning
    专注于深化战略环节:战略文档、OKRs、路线图、优先级排序。
  • 当核心需求是学习与获取证据时,使用
    discovery-research
    Skill。
  • 当核心需求是对齐目标与沟通时,使用
    stakeholder-management
    Skill。