executive-onboarding-playbook
by deanpetersUse the executive-onboarding-playbook skill to build a diagnostic 30-60-90 day plan for new VP Product or CPO leaders. It helps you validate strategy, team health, and hidden risks before making changes, with a practical executive-onboarding-playbook guide for Playbooks users.
This skill scores 82/100, which means it is a solid directory listing for users who need a structured executive onboarding workflow. The repository gives enough trigger guidance, phased process detail, and example context that an agent can use it with less guesswork than a generic prompt, though it is still more playbook than fully instrumented toolchain.
- Strong triggerability for a specific use case: entering a new VP or CPO role, evaluating an offer, or diagnosing an inherited org.
- Clear operational framing across three phases—Diagnose, Validate, Act with Evidence—so an agent can follow the workflow in sequence.
- Useful install-decision value from the example file, which shows how the playbook applies in a realistic VP Product onboarding scenario.
- No install command, scripts, or companion references, so adoption depends on reading and manually applying the SKILL.md guidance.
- The repository is workflow-heavy but not deeply procedural at the step level; some execution still requires agent judgment and synthesis.
Overview of executive-onboarding-playbook skill
The executive-onboarding-playbook skill helps a new VP Product, CPO, or product executive structure the first 90 days as a diagnostic process before making big changes. It is best for leaders who need to understand the org, pressure-test assumptions, and avoid the common failure mode of moving too fast on strategy, people, or process.
What this skill is for
Use executive-onboarding-playbook when you need a disciplined 30-60-90 day plan that starts with evidence, not opinions. The real job-to-be-done is to turn a vague “what should I do first?” prompt into an onboarding plan that reveals team health, decision-making patterns, unwritten strategy, and operating risks.
Who should install it
The executive-onboarding-playbook skill is a strong fit if you are:
- stepping into a first-time executive product role
- preparing for a CPO interview or offer
- inheriting a team with unclear ownership or mixed signals
- trying to decide what to change after the first few weeks
Why it differs from a generic prompt
This is not just a “make me a 90-day plan” prompt. The executive-onboarding-playbook for Playbooks centers diagnostic sequencing: Month 1 diagnose, Month 2 validate, Month 3 act with evidence. That makes it more useful when the risk is premature restructuring, not lack of effort.
How to Use executive-onboarding-playbook skill
Install it and inspect the source
To install the executive-onboarding-playbook install, use the repo path shown in the skill metadata, then open skills/executive-onboarding-playbook/SKILL.md first. Also review examples/sample.md to see how the playbook is applied in a realistic executive transition.
Give the skill a concrete role and context
The executive-onboarding-playbook usage works best when you specify:
- the role: VP Product, CPO, or similar
- company stage and type
- what is already known about the org
- the main concern: team health, strategy clarity, hiring, or stakeholder alignment
Stronger input example: “I’m starting as VP Product at a Series B B2B SaaS company. The roadmap is noisy, Sales and Product disagree on priorities, and I need a 90-day plan that avoids premature re-orgs.”
Read the files in the right order
For a practical executive-onboarding-playbook guide, start with:
SKILL.mdfor the core workflow and phase logicexamples/sample.mdfor a complete worked example- any linked supporting files if the repo adds them later
Focus on the sections about purpose, key concepts, and the consultant mindset, because those explain how to think, not just what to do.
Prompt it for evidence, not platitudes
When using the skill, ask for outputs such as:
- a 30-60-90 day diagnostic plan
- interview questions for executives and cross-functional partners
- a memo template for findings and risks
- decision points for when to act, wait, or validate further
If you only ask for “onboarding advice,” you will get generic guidance. If you ask for “a diagnostic onboarding plan with risks, assumptions, and evidence checks,” the output will be materially better.
executive-onboarding-playbook skill FAQ
Is this only for Product leaders?
Mostly yes. The executive-onboarding-playbook skill is designed around executive product leadership, especially VP and CPO transitions. It may still help adjacent leaders, but the strongest fit is for product executives who need to assess org dynamics and strategy before changing them.
How is this different from a normal 30-60-90 template?
A normal template often assumes execution starts immediately. The executive-onboarding-playbook skill is built around diagnosis first: learn the system, identify hidden constraints, then choose interventions. That matters when the biggest risk is acting on incomplete information.
Is it beginner-friendly?
Yes, if “beginner” means new to executive onboarding. It is not a technical skill or a coding workflow, so the main requirement is willingness to gather evidence and challenge first impressions. If you want a simple checklist with no stakeholder interviews, this is probably not the right fit.
When should I not use it?
Do not use the executive-onboarding-playbook for Playbooks if your job is already defined by a strict deliverable plan, or if you need a tactical execution roadmap for a stable team. It is most valuable when the org is ambiguous, politically sensitive, or likely to tempt you into moving too soon.
How to Improve executive-onboarding-playbook skill
Provide better starting assumptions
The quality of the executive-onboarding-playbook usage depends on how clearly you describe the situation. Include what you know about the CEO’s expectations, the previous leader’s exit, the current team shape, and any hard constraints such as hiring freezes, roadmap commitments, or major customer issues.
Ask for the outputs you will actually use
Instead of asking for a broad onboarding plan, ask for specific artifacts:
- a first-30-days interview plan
- an executive alignment checklist
- a risk register
- a Month 1 findings memo
- a “what to change vs what to observe” decision framework
That forces the skill to produce something actionable rather than inspirational.
Watch for the common failure mode
The biggest failure mode is over-indexing on visible process problems and under-reading the unwritten strategy. If the first answer feels too confident, ask it to separate facts, inferences, and open questions. That usually improves the executive onboarding plan more than asking for more detail.
Iterate after the first draft
Use the first output to refine the plan with real-world data. If interviews reveal contradictions, feed those back into the skill and ask for updated priorities, revised hypotheses, and a sharper 90-day decision plan. That is where executive-onboarding-playbook skill becomes most valuable.