Director 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: 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.

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)

---

### 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; something isn't clicking the way it should

**Or describe your situation directly.**

---

### Branch 1: Preparing to Make the Leap

#### Question 1B (Q2/3):

**Agent asks:**

"What's the gap you most want to close before making the move?"

1. **Thinking altitude** — I still default to solving customer problems directly instead of designing systems
2. **Stakeholder navigation** — I struggle with organizational politics, executive dynamics, or cross-functional influence
3. **Strategic narrative** — I can't yet connect my work to company strategy convincingly in conversations with leadership
4. **Direction creation** — I wait for clarity from above rather than creating it for my team

**Or describe your main development area.**

#### Questio

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.