director-readiness-advisor by deanpeters/product-manager-skills
npx skills add https://github.com/deanpeters/product-manager-skills --skill director-readiness-advisor通过适应性问题和针对性指导,帮助产品经理和总监应对从产品经理到总监转型过程中的具体挑战。诊断您所处的转型阶段,并提供基于实际情况、有实战经验支撑的实用指导,而非通用的领导力建议。
这不是一份准备清单。这是一次指导对话,旨在明确指出实际困难所在、原因以及应对方法。
从产品经理到总监的转型,根据您所处的阶段,呈现出不同的面貌:
每种情境都有不同的指导重点。最大的错误是将适用于"新官上任"的建议套用在已任职两年的总监身上,或将"准备"阶段的建议用于正在面试过程中的人。
本技能直接基于"高度与视野框架"——完整的思维模型请参阅 skills/altitude-horizon-framework/SKILL.md。此处使用的核心概念包括:
使用 workshop-facilitation 作为本技能的默认交互协议。
它定义了:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
其他(请说明))本文件定义了特定领域的评估内容。如果存在冲突,请遵循本文件的领域逻辑。
这个互动技能会提出 1 个诊断性问题 + 最多 3 个适应性跟进问题,然后根据您的情况提供 3–5 条编号的、有针对性的建议。
Agent 说:
开始之前,您可以选择如何运行本次会话:
Agent 提问(Q1/3):
"您在从产品经理到总监的旅程中处于哪个阶段?"
或者直接描述您的情况。
Agent 提问:
"在迈出这一步之前,您最想弥补的差距是什么?"
或者描述您的主要发展领域。
Agent 提问:
"您的准备时间还有多久——距离迈出这一步有多近?"
或者描述您的时间表。
Agent 提供(基于 1B + 1C):
示例输出(针对 1B = 战略叙事 + 1C = 3–6个月):
"根据您的差距(战略叙事)和时间表(3–6个月),以下是您最高杠杆率的行动:
重构您的 1 对 1 对话 —— 从汇报战术进展转向提出战略性问题:'我的工作如何与公司今年试图实现的目标联系起来?有哪些我尚未看到的组织背景?' 这既能锻炼战略思维肌肉,又能同时向您的经理发出准备就绪的信号。
现在就建立您的战略分解习惯 —— 从上一次季度业务回顾或全员会议中选取一个公司优先事项,并撰写一份一页纸的解读:您团队的工作如何与之关联?非正式地与您的经理分享。您不需要获得许可来练习这项技能。
审视您的英雄主义倾向 —— 跟踪接下来两周:您有多少次跳进去解决那些别人在您的指导下就能解决的问题?'救援'与'培养'的比例是总监准备就绪的领先指标。
不要过度关注总监思维 —— 在仍是产品经理时最常见的错误是:在高度/视野思维上花费过多精力,以至于影响了当前角色的职责履行。充分扮演好您的产品经理角色。总监准备就绪将体现在您的工作质量上,而不是在超越您当前层级的表演上。
选择一个编号以深入了解其中任何一项,或询问具体内容。"
Agent 提问:
"您的面试背景是什么?"
Agent 提问:
"您最想在面试准备中重点提升哪方面?"
或者描述您最需要什么。
Agent 提供(基于 2B + 2C):
示例输出(针对 2B = 外部 + 2C = 练习回答):
"最有效的总监面试准备不是背诵答案——而是内化这种思维方式,使其自然流露。这两项技能是您的准备工具:
将 altitude-horizon-framework 作为学习课程来研读 —— 不要只是阅读。在每一部分之后,停下来回答:'在我自己的工作中,我在哪个高度或视野上运作过?我在这里有什么故事?' 四个转型区域和命名的失败模式几乎直接映射到常见的总监面试问题。
将此顾问作为模拟练习 —— 即使您已经在面试,也请完成分支 1(准备跃升)的练习。它揭示的发展行动正是面试官要考察的能力。如果您无法完成这个练习,说明您还没有构建出答案。
为每个转型区域构建一个故事 —— 高度与视野框架给了您四个区域;您至少需要为每个区域准备一个具体、明确的故事。使用区域名称作为结构:'有一次我需要转变思维高度……是什么触发了角色转变……有一次我必须创造方向而不是等待指示。' 面试官会立即识别出这种自我认知。
用总监语言重新表述您的产品经理成就 —— 您几乎肯定有相关经验;只是表述方式不对。不要以'我交付了 X'开头。以'我的团队当时面临的战略问题是 [X]。以下是我对产品组合权衡的思考方式'开头。将功能或成果作为证据,而不是标题。
诚实地准备关于差距的问题 —— 如果您没有管理过直接下属、没有负责过预算、或者没有在产品组合层面运作过,不要回避。最有力的回答是:'这是我的差距,以下是我一直在为此做的准备,以及我在前 90 天会重点学习的内容。' 诚实且有计划的回答远比回避要好得多。
选择一个编号以深入了解,或描述您想练习什么。"
Agent 提问:
"您目前最紧迫的挑战是什么?"
或者描述最紧迫的问题。
Agent 提问:
"您的团队情况如何?"
Agent 提供(基于 3B + 3C):
示例输出(针对 3B = 方向不明确 + 3C = 继承团队):
"一个没有明确方向的继承团队,是前 90 天最常见的总监失败模式。以下是应对方法:
本周内进行一次战略背景分解图 —— 不要等待来自上级的完美清晰度。选取您最近听到的公司优先事项(季度业务回顾、全员会议、您经理陈述的目标),并将其向下分解:这对您的业务单元、您的产品组合、您团队的具体职责意味着什么?一页纸。分享它。当您了解更多信息时修订它。
立即重构您的 1 对 1 会议 —— 大多数继承的团队会利用 1 对 1 会议向您汇报功能状态和战术优先级。请重新引导:'我想了解您的每个产品如何与我负责的业务目标联系起来。帮助我看到其中的关联。' 这从第一天起就确立了高度。
明确地向您的团队说明模糊性 —— 不要假装您拥有实际上没有的清晰度。'我仍在构建我对领导层期望我们走向何方的图景。这是我目前的最佳解读。我会在两周后更新它。' 团队宁愿拥有诚实的部分背景信息,也不愿保持沉默。
在理解之前,抵制重组的冲动 —— 对于继承的团队,本能反应是按照您的想法重组流程和结构。等待 60–90 天。在改变之前,先了解哪些是有效的以及为什么有效。房间里的猴子并不总是错的——有些猴子建造了这个地方。
选择一个编号以深入了解,或描述最阻碍您的是什么。"
Agent 提问:
"核心摩擦点是什么?目前哪个方面让您感觉角色最不顺畅?"
或者描述哪些方面运作不畅。
Agent 提问:
"您担任这个总监职位多久了?"
Agent 提供(基于 4B + 4C):
示例输出(针对 4B = 仍然表现得像个产品经理 + 4C = 1–2 年):
"一个在 12 个月以上仍在做独立贡献者工作的总监不是在转型——他们已经陷入了一种不可持续的混合角色。以下是诊断和修复方法:
精确命名英雄主义模式 —— 跟踪接下来两周:您有多少时间花在解决问题上,而不是培养解决问题的人上?处于这种模式的大多数总监有 60–70% 的时间在做独立贡献者工作。目标应接近 20%。
识别是什么让您陷入其中 —— 通常有三个原因:(a) 您更信任自己的判断而不是团队的判断,(b) 团队没有得到足够的发展,无法在没有您的情况下负责事务,(c) 您获得的奖励信号(表扬、可见性)强化了独立贡献者行为。是哪一种?
为您最常做的 3 项独立贡献者活动制定有计划的交接 —— 列出您最常做的三件本应由产品经理负责的事情。对于每一项:写下'做得好'是什么样子,与负责的产品经理进行一次关于由其负责的对话,然后在他们遇到困难时不要'救援'。通过失败进行指导就是您的工作。
改变奖励循环 —— 您作为产品经理获得的表扬,在担任总监时不会再有。总监的成功更安静,也更延迟。寻找新的信号:一个产品经理独自完成了艰难的利益相关者沟通,一个团队创建了自己的背景分解图,一个您做出的产品组合决策在压力下经受住了考验。开始注意这些胜利。
如果这种模式在 1–2 年后已经根深蒂固,请考虑这个角色是否适合您 —— 有些人作为高级独立贡献者或首席产品经理会更快乐、更高效。这不是失败——这是自我认知。独立贡献者路径是合理的;不匹配的是留在总监职位上却以产品经理的方式运作。
选择一个编号以深入了解,或告诉我您接下来想做什么。"
完整的端到端交互,包括情境输入、分支选择和最终建议,请参阅 examples/conversation-flow.md。
Q1: "3 — 新官上任" Q2: "3 — 方向不明确" Q3: "1 — 继承了一个成熟的团队"
Agent 输出: 战略背景分解图说明、关于重构 1 对 1 会议的建议、明确说明模糊性以及抵制过早重组。链接到 altitude-horizon-framework 获取完整的分解模板。
Q1: "1 — 准备跃升" Q2: "3 — 战略叙事" Q3: "2 — 3–6个月"
Agent 输出: 1 对 1 会议重构策略、战略分解习惯建立练习、英雄主义倾向审视,以及警告在仍是产品经理时不要过度关注总监思维。
症状: 询问"我需要做什么才能获得晋升?"并像完成任务一样处理清单项目
后果: 您优化的是准备就绪的表象,而不是建立实际的能力。面试官和经理能看出区别。
解决方法: 使用此顾问来确定对您的情况最重要的一两个具体行为改变,而不是一个全面的发展计划。
症状: 当您实际上处于积极的面试过程中时选择"准备跃升",或者当您已任职 18 个月时选择"新官上任"
后果: 您得到的指导是针对错误情境校准的。
解决方法: 诚实地面对您实际所处的位置,而不是您希望的位置。
症状: 询问此顾问您是否"准备好"转型
后果: 没有准备就绪测试。转型是一个决定,而不是毕业。
解决方法: 使用此技能来确定对您个人来说最困难的是什么以及如何应对——而不是为了获得通过/失败的裁决。
skills/altitude-horizon-framework/SKILL.md —— 本技能所指导的思维模型;包含战略背景分解图模板skills/workshop-facilitation/SKILL.md —— 此互动技能的引导协议director-to-vp-cpo-advisor(计划中)—— 指导下一个转型:总监到产品副总裁或首席产品官每周安装量
177
代码库
GitHub 星标数
1.5K
首次出现
10 天前
安全审计
安装于
codex159
opencode158
github-copilot156
gemini-cli155
kimi-cli154
amp154
Guide PMs and Directors through the specific challenges of the PM-to-Director transition using adaptive questions and targeted coaching. Diagnoses where you are in the journey and delivers practical, war-story-backed guidance calibrated to your situation — not generic leadership advice.
This is not a readiness checklist. It's a coaching conversation that names what's actually hard, why it's hard, and what to do about it.
The PM → Director transition looks different depending on where you are:
Each situation has distinct coaching priorities. The biggest mistake is applying "newly landed" advice to someone who's been in the role for two years, or "preparing" advice to someone mid-interview process.
This skill draws directly on the Altitude & Horizon Framework — see skills/altitude-horizon-framework/SKILL.md for the full mental model. Core concepts used here:
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks 1 diagnostic question + up to 3 adaptive follow-up questions , then delivers 3–5 enumerated, targeted recommendations based on your situation.
Agent says:
Before we start, you can choose how to run this session:
Agent asks (Q1/3):
"Where are you in the PM-to-Director journey?"
Or describe your situation directly.
Agent asks:
"What's the gap you most want to close before making the move?"
Or describe your main development area.
Agent asks:
"What's your runway — how close are you to making the move?"
Or describe your timeline.
Agent delivers (based on 1B + 1C):
Example output for 1B = Strategic narrative + 1C = 3–6 months:
"Based on your gap (strategic narrative) and timeline (3–6 months), here are your highest-leverage moves:
Reframe your 1-on-1 conversations — Shift from reporting tactical progress to asking strategic questions: 'How does my work connect to what the business is trying to do this year? What's the organizational context I'm not seeing?' This builds strategic thinking muscle and signals readiness to your manager simultaneously.
Build your cascade habit now — Pick one company priority from the last QBR or all-hands and write a one-page translation: how does your team's work connect? Share it informally with your manager. You don't need permission to practice this skill.
Audit your Hero Syndrome — Track the next two weeks: how often do you jump in to solve problems that others could solve with your coaching instead? The ratio of rescuing to developing is a leading indicator of Director readiness.
Don't over-index on Director thinking — The most common mistake while still a PM: spending too much energy on altitude/horizon thinking at the expense of serving your current role. Play your PM role fully. Director readiness will show in the quality of your work, not in performing above your level.
Choose a number to go deeper on any of these, or ask about something specific."
Agent asks:
"What's your interview context?"
Agent asks:
"What do you most want to work on for interview prep?"
Or describe what you most need.
Agent delivers (based on 2B + 2C):
Example output for 2B = External + 2C = Practicing responses:
"The most effective Director interview prep isn't memorizing answers — it's internalizing the thinking so it comes out naturally. These two skills are your prep tools:
Work throughaltitude-horizon-framework as a study session — Don't just read it. After each section, pause and answer: 'Where have I operated at this altitude or horizon in my own work? What's my story here?' The Four Transition Zones and Named Failure Modes map almost directly to common Director interview questions.
Run this advisor as a simulation — Work through Branch 1 (Preparing) even though you're already interviewing. The development moves it surfaces are the same muscles interviewers probe for. If you can't do the exercise, you haven't yet built the answer.
Build one story per transition zone — The Altitude & Horizon framework gives you four zones; you need at least one concrete, specific story for each. Use the zone names as the structure: 'Here's a time I had to shift my thinking altitude... here's what triggered the persona shift... here's when I had to create direction rather than wait for it.' Interviewers recognize this kind of self-awareness immediately.
Reframe your PM wins in Director language — You almost certainly have the experience; it's framed wrong. Don't open with 'I shipped X.' Open with: 'The strategic question my team was facing was [X]. Here's how I thought about the portfolio tradeoff.' Use the feature or outcome as evidence, not as the headline.
Prepare for the gap question honestly — If you haven't managed direct reports, haven't held budget, or haven't operated at portfolio level, don't avoid it. The strongest answer is: 'Here's the gap, here's how I've been developing toward it, and here's what I'd focus on learning in the first 90 days.' Honesty with a plan lands significantly better than avoidance.
Choose a number to go deeper, or describe what you want to practice."
Agent asks:
"What's your most pressing challenge right now?"
Or describe what's most pressing.
Agent asks:
"What's your team situation?"
Agent delivers (based on 3B + 3C):
Example output for 3B = Direction is unclear + 3C = Inherited team:
"An inherited team without clear direction is the most common Director failure mode in the first 90 days. Here's what to do:
Run a Cascading Context Map this week — Don't wait for perfect clarity from above. Take the most recent company priority you heard (QBR, all-hands, your manager's stated objectives) and translate it down: what does it mean for your business unit, your portfolio, your team's specific accountabilities? One page. Share it. Revise it when you learn more.
Reframe your 1-on-1s immediately — Most inherited teams will use 1-on-1s to brief you on feature status and tactical priorities. Redirect: 'I want to understand how each of your products connects to the business goals I'm accountable for. Help me see the through-line.' This establishes altitude from day one.
Name the ambiguity explicitly to your team — Don't pretend you have clarity you don't have. 'I'm still building my picture of where leadership wants us to go. Here's my best current translation. I'll update it in two weeks.' Teams would rather have honest partial context than silence.
Resist the urge to reorganize before you understand — With an inherited team, the instinct is to reorganize processes and structures to reflect how you think. Wait 60–90 days. Understand what's working and why before you change it. The monkeys in the room aren't always wrong — some of them built the place.
Choose a number to go deeper, or describe what's most blocking you."
Agent asks:
"What's the core friction? Where does the role feel most broken right now?"
Or describe what's not working.
Agent asks:
"How long have you been in this Director role?"
Agent delivers (based on 4B + 4C):
Example output for 4B = Still acting like a PM + 4C = 1–2 years:
"A Director who is still doing IC work after 12+ months isn't transitioning — they've settled into an unsustainable hybrid role. Here's the diagnosis and the fix:
Name the Hero Syndrome pattern precisely — Track the next two weeks: how much of your time is spent solving problems versus developing people who solve problems? Most Directors in this pattern are at 60–70% IC work. The target is closer to 20%.
Identify what's keeping you in it — There are usually three causes: (a) you trust your own judgment more than your team's, (b) the team hasn't been developed enough to own things without you, (c) you're getting reward signals (praise, visibility) that reinforce the IC behavior. Which one is it?
Create a deliberate handoff for your top 3 IC activities — List the three things you do most often that a PM should own. For each: write down what 'done well' looks like, have a conversation with the PM about owning it, and then don't rescue when they struggle. Coaching through failure is the work.
Change the reward loop — The pat-on-the-back you got as a PM doesn't come as a Director. Director success is quieter and more delayed. Find the new signal: a PM who ships a difficult stakeholder conversation alone, a team that creates its own context cascade, a portfolio decision you made that held up under pressure. Start noticing those wins.
If this pattern is entrenched at 1–2 years, consider whether the role is the right fit — Some people are happier and more effective as senior ICs or Principal PMs. That's not failure — it's self-knowledge. The IC path is legitimate; the mismatch is staying in a Director role while operating as a PM.
Choose a number to go deeper, or tell me what you want to work on next."
See examples/conversation-flow.md for a full end-to-end interaction, including context intake, branch selection, and final recommendations.
Q1: "3 — Newly landed" Q2: "3 — Direction is unclear" Q3: "1 — Inherited an established team"
Agent output: Cascading Context Map instructions, advice on reframing 1-on-1s, naming ambiguity explicitly, and resisting premature reorganization. Links to altitude-horizon-framework for the full cascade template.
Q1: "1 — Preparing to make the leap" Q2: "3 — Strategic narrative" Q3: "2 — 3–6 months"
Agent output: 1-on-1 reframe tactics, cascade habit-building exercise, Hero Syndrome audit, and warning against over-indexing on Director thinking while still in PM role.
Symptom: Asking "what do I need to do to get promoted?" and working through items like tasks
Consequence: You optimize for appearances of readiness rather than building the actual muscles. Interviewers and managers can tell the difference.
Fix: Use this advisor to identify the one or two specific behavior changes that matter most for your situation, not a comprehensive development program.
Symptom: Selecting "preparing" when you're actually in an active interview process, or selecting "newly landed" when you've been in the role 18 months
Consequence: You get coaching calibrated to the wrong situation.
Fix: Be honest about where you actually are, not where you'd like to be.
Symptom: Asking this advisor whether you're "ready" for the transition
Consequence: There's no readiness test. The transition is a decision, not a graduation.
Fix: Use this skill to identify what will be hardest for you specifically and how to address it — not to get a pass/fail verdict.
skills/altitude-horizon-framework/SKILL.md — The mental model this skill coaches on; includes the Cascading Context Map templateskills/workshop-facilitation/SKILL.md — Facilitation protocol for this interactive skilldirector-to-vp-cpo-advisor (planned) — Coaches the next transition: Director to VP or CPO of ProductWeekly Installs
177
Repository
GitHub Stars
1.5K
First Seen
10 days ago
Security Audits
Gen Agent Trust HubPassSocketFailSnykPass
Installed on
codex159
opencode158
github-copilot156
gemini-cli155
kimi-cli154
amp154
Google Workspace CLI 团队负责人技能:自动化站会、任务协调与团队沟通工具
6,300 周安装