Vp Cpo Readiness AdvisorSAFE

Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: vp-cpo-readiness-advisor
argument-hint: "[where you are in the transition]"
description: Guide the transition to VP or CPO across preparing, interviewing, landing, and recalibrating. Use when executive product scope is changing fast.
intent: >-
  Guide Directors and senior product leaders through the specific challenges of the transition to VP or CPO using adaptive questions and targeted coaching. Diagnoses where you are in the journey and delivers practical, lived-experience coaching calibrated to your situation — not generic executive advice.
type: interactive
theme: career-leadership
best_for:
  - "Preparing for the Director-to-VP or VP-to-CPO transition"
  - "Evaluating a VP or CPO role before you accept it"
  - "Recalibrating when something isn't working in an executive product role"
scenarios:
  - "I'm a Director preparing for VP roles and want to understand what actually changes"
  - "I have a CPO offer I'm evaluating — what are the right questions to ask the CEO?"
  - "I've been a VP for 18 months and my executive peer relationships aren't working"
estimated_time: "15-20 min"
---

## Purpose

Guide Directors and senior product leaders through the specific challenges of the transition to VP or CPO using adaptive questions and targeted coaching. Diagnoses where you are in the journey and delivers practical, lived-experience coaching calibrated to your situation — not generic executive advice.

The VP/CPO transition is not a continuation of the Director transition. The landscape changes. Strategy becomes largely unwritten. Your primary customer may shift. You stop using product language with executives. Constraints don't disappear — the Rubik's Cube just goes from 3×3 to 9×9. This advisor names what's actually hard at this level and what to do about it.

## Input

**Works best with:** Where you are in the Director-to-VP/CPO journey: preparing, interviewing, newly landed, or recalibrating.
**Also useful:** Company stage, whether you'd be (or are) the first product executive, and your relationship with the CEO.

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 advisor opens by asking which of the four situations describes you, then branches.

**Example invocation:** `I have a CPO final-round interview with a founder-CEO who has strong product opinions — help me prepare.`

## Key Concepts

### The Three Ps Framework

At VP and CPO level, your accountability expands across three dimensions simultaneously:

- **Product** — Portfolio decisions, roadmap strategy, product family coherence
- **Practice** — How the work gets done; process discipline, execution consistency, cross-functional operating rhythms
- **People** — The dominant focus at this level: org structure, talent matching, developing leaders, setting expectations and inspecting them

Most Directors are strong in Product and adequate in Practice. The People dimension — not managing individuals but stewarding the organizational system — is where the VP/CPO transition most often breaks down.

---

### The Empowerment Myth

The most common false belief about promotion to VP or CPO: "Once I get there, I'll finally be empowered. I'll have the authority to do what I always knew needed to be done."

The reality: constraints don't disappear. They change shape. A PM's Rubik's Cube is 3×3. A Director's is 5×5. A VP's is 7×7. A CPO's is 9×9. The same principles apply — you're still balancing competing priorities, navigating stakeholder dynamics, and making decisions with incomplete information. The blast radius of each decision just gets exponentially larger.

The leaders who thrive at VP/CPO level are the ones who made peace with this: you're not escaping constraints. You're developing the capacity to navigate larger ones.

---

### The VP → CPO Paradigm Shift

The most significant cognitive reframe in the entire product leadership track:

**VP mindset:** "What are we releasing? How does our product portfolio perform? What's the roadmap?"
**CPO mindset:** "What business outcomes are we accountable for, and how does the product organization achieve them?"

Practical consequences of this shift:
- **Language changes deliberately.** Stop using product language (features, roadmaps, user stories, sprints) in executive forums. Switch to business language (ROI, revenue, retention, margin, EBITDA). Reserve product vocabulary for conversations with your product team.
- **Your primary "customer" may shift.** At a company pursuing exit or growth financing, the CPO's primary customer may be the investor or buyer — not the end user. The persona you optimize for depends on the business context.
- **Your team shifts.** As CPO, your most important team is not the product organization. It's the executive staff — CEO, CFO, CRO, CMO. These are the relationships that determine whether the product organization gets what it needs to succeed.

---

### Time Horizon Expansion

| Level | Short-term | Long-term |
|---|---|---|
| Individual Contributor | Sprint | Quarter |
| Director | Quarter | 1–2 years |
| VP | 1–2 quarters | 3 years |
| CPO | 1–2 quarters | 3–5 years |

One thing doesn't change: you still have to deliver every quarter. The long-term horizon doesn't replace the short-term accountability — it runs in parallel. "Sweeping up after the elephants" (the unglamorous, necessary quarterly work) is still part of the job at CPO level. The difference is that you're also responsible for knowing where the parade is going three years from now.

---

### Alliance Building at Executive Level

At Director level, you manage down and influence laterally. At VP/CPO level, the executive team becomes your primary operating environment — and alliances are not optional.

Without them, you're a "dead man walking." Executives can appear supportive in mee

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.