Skip to content
Productivity
Skill

/director-readiness-advisor

Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

From plugin
product-manager-skills
7.8k77 skills6 commands

Claude Code

$ npx -y skills add deanpeters/Product-Manager-Skills --skill director-readiness-advisor --agent claude-code

SKILL.md

director-readiness-advisor.SKILL.md
name: director-readiness-advisor
argument-hint: "[where you are: preparing | interviewing | landed | recalibrating]"
description: Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.
intent: >-
  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.
type: interactive
theme: career-leadership
best_for:
  - "Preparing to make the leap to Director over the next 3-12 months"
  - "Navigating your first 6 months in a new Director role"
  - "Diagnosing what isn't working 12+ months into the Director role"
scenarios:
  - "I'm a senior PM preparing for Director interviews next quarter"
  - "I just got promoted to Director and I can't stop jumping into the tactical work"
  - "I've been a Director for 18 months and my exec relationships aren't working"
estimated_time: "10-15 min"

Purpose

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.

Input

**Works best with:** Where you are in the PM-to-Director journey: preparing for the jump, interviewing, newly landed, or recalibrating after a rough start. **Also useful:** Your org context (team size, who you'd report to) and the specific friction you're feeling.

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'm 60 days into a Director role and my old peers now report to me — it's awkward and I'm still doing PM work. Coach me.`

Key Concepts

The Four Transition Situations

The PM → Director transition looks different depending on where you are:

1. **Preparing to make the leap** — Still a PM, actively developing toward the role 2. **Interviewing for Director roles** — In an active internal or external search 3. **Newly landed** — Recently promoted or hired as Director (first 6 months) 4. **Recalibrating** — Been a Director for a while; something isn't working

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.

The Underlying Model

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:

  • Altitude (scope) and Horizon (time) as the two axes that shift
  • The Waiter vs. Restaurant Operator distinction
  • Four transition zones: Thinking Altitude, Persona Shift, Hero Syndrome Recovery, Direction Creation
  • Named failure modes: Hero Syndrome, Allergic to Process, People-Pleaser Leadership, Instant Gratification Trap

---

Facilitation Source of Truth

Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.

**Default entry mode:** Guided · set in `pm-skills.config.yaml` (library-wide default or a per-skill override); the user's own choice in the session always wins. On the first turn, offer all three modes, then open in the default without waiting for a pick: Guided asks the first question, Context dump invites the paste, Best guess asks for a one-sentence minimum and drafts with every assumption labeled.

It defines:

  • Session heads-up + entry mode (Guided, Context dump, Best guess)
  • One-question turns with plain-language prompts
  • Progress labels (e.g., Context Q1/3)
  • Interruption handling and pause/resume behavior
  • Numbered recommendations at decision points
  • Quick-select numbered response options (include `Other (specify)` when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

---

Application

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.

---

Step 0: Session Start

**Agent says:**

Before we start, you can choose how to run this session:

1. **Guided** — I'll ask questions one at a time and build recommendations from your answers (recommended for most situations) 2. **Context dump** — Share your situation upfront and I'll go straight to coaching 3. **Best guess** — Tell me nothing; I'll give you the highest-value advice for the most common transition situation (newly landed Director, 0–3 months in)

**Same turn, don't wait for a mode pick:** open in this skill's default entry mode (the `Default entry mode` line). If it's Guided, ask Question 1 (Q1/3) right after the options. If it's Context dump, invite the paste. If it's Best guess, ask for a one-sentence minimum and start drafting. Switch as soon as the user picks a different mode.

---

Question 1: Where Are You?

**Agent asks (Q1/3):**

"Where are you in the PM-to-Director journey?"

1. **Preparing to make the leap** — Still in a PM role, actively building toward Director 2. **Interviewing for Director roles** — In an active internal promotion or external job search 3. **Newly landed** — Recently promoted or hired as Director (roughly first 6 months) 4. **Recalibrating** — Been a Director for a while;

Read more
@deanpeters
Ships withproduct-manager-skills

77 battle-tested PM frameworks, ready for Claude, Codex, ChatGPT, and any agent that can read structured knowledge.

Stars on GitHub

Momentum

stars in total
7.8k
Star history of deanpeters/Product-Manager-Skills on GitHub, a chart by star-history.com

Other skills on product-manager-skills.

More skills from other plugins.

i-have-adhd

i-have-adhd

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…

@ayghri@ayghriInstall Skill
ab-test-analysis

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop…

@phuryn@phurynInstall Skill
distilly

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…

Questions about director-readiness-advisor.

Which coding agents can use director-readiness-advisor?
director-readiness-advisor installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.