SkillAgentSearch skills...

executive-onboarding-playbook

Plan a VP or CPO 30-60-90 day diagnostic onboarding path

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill executive-onboarding-playbook

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of executive-onboarding-playbook

executive-onboarding-playbook scores 83/100 on our quality scale, 57th of 82 Project & Program Management skills we index.

Its SKILL.md is 19 KB long, well organised into 26 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
8/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so executive-onboarding-playbook is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

executive-onboarding-playbook compared with similar skills

All 4 of these similar skills score higher than executive-onboarding-playbook; compare them before choosing.

SkillScoreStarsUpdatedFormat
executive-onboarding-playbook (this skill)by deanpeters837.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install executive-onboarding-playbook?
Run npx skills add deanpeters/Product-Manager-Skills --skill executive-onboarding-playbook. The install tabs above show the steps for each supported agent.
Which AI agents does executive-onboarding-playbook work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is executive-onboarding-playbook safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is executive-onboarding-playbook still maintained?
The repository was last updated about 3 months ago, so executive-onboarding-playbook is actively maintained.

name: executive-onboarding-playbook argument-hint: "[role and company context]" description: Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change. intent: >- Structure the first 90 days of a VP or CPO transition as a diagnostic process, not an execution sprint. The single most common failure in senior product leadership transitions is acting before understanding — changing structures, replacing people, or announcing strategy before building the evidence base that makes those decisions defensible. type: workflow theme: career-leadership best_for:

  • "Starting a new VP or CPO role in the first 90 days"
  • "Evaluating a CPO offer — what to ask before you accept"
  • "Diagnosing an organization you've just inherited" scenarios:
  • "I just accepted a VP of Product role starting next month — help me plan my first 90 days"
  • "I'm evaluating a CPO offer and want to know what questions to ask the hiring CEO"
  • "I'm two months into a new role and want to validate what I've learned before I start acting" estimated_time: "20-30 min"

Purpose

Structure the first 90 days of a VP or CPO transition as a diagnostic process, not an execution sprint. The single most common failure in senior product leadership transitions is acting before understanding — changing structures, replacing people, or announcing strategy before building the evidence base that makes those decisions defensible.

This playbook runs in three phases: Diagnose (Month 1), Validate (Month 2), Act with Evidence (Month 3). Each phase builds on the last. Skipping phases doesn't accelerate results — it guarantees expensive reversals.

This is not a 100-day plan for impressing your new boss. It's a diagnostic protocol for making durable decisions.

Input

Works best with: The role you're stepping into (VP or CPO) and basic company context — size, stage, how the product org is set up. Also useful: How far you are from Day 1 (offer stage, pre-start, week 3), known landmines, and what the CEO says success looks like.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The playbook opens by asking your start date and company context, then anchors you in the right phase.

Example invocation: I start as VP Product at a 300-person Series C in 3 weeks — first product exec hire, founder currently runs product. Build my 30-60-90.

Key Concepts

The Consultant Mindset

Enter every new VP/CPO role as if you're an external consultant hired to assess the organization — before you're the person responsible for changing it.

What this means in practice:

  • Observe before diagnosing. Don't form opinions in the first week based on first impressions.
  • Ask questions before making declarations. "Help me understand how this works" is more powerful than "here's what we're going to do differently."
  • Understand how the steering connects to the rudder. In any organization, there are systems and relationships that look one way on paper and work completely differently in practice. Map that reality before you touch anything.
  • Don't throw the big red switch. If you walked into a power plant you'd never operated before and saw a large red switch, you probably wouldn't throw it. The same logic applies to org structures, processes, reporting lines, and team compositions you've inherited. Understand what they control first.

Negotiate this upfront: tell your boss and peers that Month 1 is explicitly a learning phase. Set the expectation that your first major recommendations will come in Month 2. Executives who've been through transitions will respect this; executives who want action in Week 1 are a signal worth noting.


Unwritten Strategy

At VP and CPO level, significant strategy is never fully written down. It lives in:

  • The CEO's head, shaped by conversations you weren't in
  • Board meeting dynamics and investor preferences
  • Last night's executive dinner
  • Off-the-record conversations between founders
  • Tribal knowledge that long-tenured leaders treat as obvious

This isn't dysfunction — it's how every organization works at the executive level. Treating written strategy as complete strategy will get you into trouble fast.

Your job in the first 90 days is to surface the unwritten layer. How:

  • Ask indirect questions: "What's the history here?" / "How did we end up with this approach?" / "What did we try before that didn't work?"
  • Let information find you. People who want to shape the new leader's perspective will seek you out. Take those meetings. Take notes.
  • Reality-check with your boss: "Here's what I'm hearing from the organization. This is different from what you told me. Help me understand." This is not confrontational — it's how you triangulate toward the truth.

The Body of Evidence

Every significant decision you make in Month 3 and beyond should rest on a body of evidence collected in Months 1 and 2. This means:

  • Detailed notes from every diagnostic conversation
  • Patterns noted across multiple independent sources (not just one vocal person)
  • Reality-checks completed with your manager and key peers
  • A clear picture of what's working, what's broken, and why

The body of evidence is what separates confident decisions from guesses. It's also what makes hard decisions defensible — to your team, to your peers, and to the board.


People Assessment: Two Categories

Two distinct people situations require different responses:

Diamonds in the rough — Capable, undervalued people who haven't had a champion. They exist in almost every organization. You'll find them in Months 1-2 by listening for: "She's really talented but nobody gives her the hard problems" or noticing who gives you the most useful, unvarnished information in your diagnostic interviews. These people become critical early allies.

Strong people in wrong roles — Not weak performers; people whose strengths are mismatched to their current scope. This is more common in organizations that grew fast, went through acquisitions, or promoted based on tenure. A former sales rep who became a PM because they knew the product. A brilliant individual contributor managing a team that needs a coach. These situations require honest, compassionate conversations — coach up if they're coachable, find them another role, or part ways. All three outcomes are better than leaving the mismatch in place.


Phase 0: Before Day 1

If you're evaluating whether to take the role, use this phase to interview the organization before it interviews you.

Five questions to probe with the hiring CEO:

  1. "What are you expecting from the product organization in the first 90 days? The first year?" — Surfaces unrealistic transformation timelines early. Red flag: "I expect the roadmap to be fully overhauled by Q2."

  2. "Who are the all-stars on your product team, and why?" — Reveals the CEO's perceptions and biases. They're often wrong, but knowing their mental model matters.

  3. "Who has gaps, and why?" — What does the CEO believe the org's weakness is? Is it accurate?

  4. "What constraints are we working with that I should understand upfront?" — Financial, organizational, market. Understand your actual degrees of freedom before you accept.

  5. "What does success look like for this role at one year?" — Force specificity. Vague answers ("transformed the product culture") are red flags. Specific answers ("85% on-time delivery, two new enterprise accounts, one rebuilt team") are workable.

Red flags that change the calculus:

  • "You can't change the existing product roadmap" — loss of basic authority before you start
  • "We need you to transform the organization in six months" — sets you up to fail
  • Misalignment between CEO's talent assessment and what you learn elsewhere in conversations

Application

Phase 1: Diagnose (Month 1)

Objective: Build the body of evidence. Understand reality, not the official version.

Step 1: Interview everyone Schedule 30-minute conversations with your direct reports, key cross-functional peers (CRO, CFO, CMO, Engineering leadership), and a sample of the PMs in your organization. The question set is simple:

  • "What's working well that I should understand and protect?"
  • "What's not working that you've been hoping someone would fix?"
  • "What do you think I need to know that I probably won't hear in official briefings?"
  • "Who are the people in this organization I should make sure to talk to?"

Step 2: Let people find you Don't do all the seeking. Some of the most valuable information comes from people who proactively schedule time with the new leader. They have an agenda — surface it, evaluate it, and note the signal (both in what they say and in that they came to you at all).

Step 3: Take detailed notes Every conversation. Note not just content but context: who said it, what their incentive might be, whether you heard the same thing from multiple independent sources. Patterns that appear across multiple conversations are much more reliable than strong opinions from single sources.

Step 4: Resist action When you see something obviously broken in Month 1, your instinct will be to fix it. Resist. You don't yet have the context to know why it's broken, whether previous attempts to fix it failed, or what it's connected to. Note it in your evidence log instead.

Deliverable: A detailed notebook of organizational reality, not yet interpreted.


Phase 2: Validate (Month 2)

Objective: Surface patterns, challenge your emerging conclusions, identify the people situations.

Step 1: Reality-check with your boss Take your emerging picture of the organization back to your manager:

  • "I'm hearing [X] from multiple people. This is different from what I understood coming in. Help me understand the history."
  • "I'm seeing [Y] pattern across the team. Is that consistent with what you've observed?"

This is not confrontational. It's how you separate signal from noise and build a shared baseline of organizational reality.

Step 2: Map the unwritten strategy By now you've had enough conversations to start seeing the gap between stated priorities and actual organizational behavior. Ask directly: "What does the organization actually optimize for when things get hard?" The answer is usually different from the mission statement.

Step 3: Complete your people assessment By end of Month 2, you should have a preliminary read on:

  • Who your diamonds in the rough are (and how to give them more scope)
  • Who is strong but in the wrong role (and what the right conversation looks like)
  • Who is genuinely not coachable to the level the org needs (and what timeline is appropriate)

Step 4: Identify your 3-5 highest-leverage changes Not a full transformation plan — three to five specific changes that would most improve organizational effectiveness. These become your Month 3 agenda.

Deliverable: An interpreted organizational assessment with people map and initial strategic priorities.


Phase 3: Act with Evidence (Month 3)

Objective: Begin making decisions grounded in the body of evidence. Introduce structure and direction, not transformation.

Step 1: Share your organizational assessment Don't keep it private. Bring your key findings to your boss and your direct reports: "Here's what I've learned about how this organization works, where it's strong, and where it needs to develop. Here's my initial plan for the next quarter." This builds trust through transparency and surfaces disagreements before you act on them.

Step 2: Run your first Cascading Context Map Use the organizational and strategic clarity you've built to create direction f

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProject
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium