# Altitude Horizon Framework

Understand the PM-to-Director transition through altitude and horizon thinking.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill altitude-horizon-framework -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill altitude-horizon-framework -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill altitude-horizon-framework -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill altitude-horizon-framework -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Purpose

Defines the two-axis mental model that distinguishes Director-level thinking from PM thinking: **Altitude** (how wide you zoom out) and **Horizon** (how far ahead you look). Use this to understand what actually changes in the transition, diagnose which transition zone is creating friction, and apply the Cascading Context Map when organizational direction is vague or absent.

This is not a seniority hierarchy. A PM operating at the right altitude for their role is doing excellent work. A Director operating at PM altitude is leaving their actual job undone.

## Input

**Nothing required**, this is a reference framework you can read start to finish.
**Also useful:** Your current situation (role, the transition friction you're feeling, a decision you're weighing). With that, the framework can be applied directly to diagnose which transition zone you're in.

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.** Read it as a mental model; pair it with `director-readiness-advisor` for guided coaching.

**Example invocation:** `Apply the altitude-horizon framework to my situation: senior PM, just inherited two more teams, drowning in delivery detail.`

## Key Concepts

### The Two Axes

**Altitude, Scope**
- **PM altitude:** Close to the ground. Customer problems, individual features, sprint priorities, specific team dynamics.
- **Director altitude:** High-level view. Product portfolio, cross-functional systems, organizational dynamics, budget allocation, market positioning.
- The shift is not about losing empathy for customers, it's about zooming out to see the entire restaurant, not just one table.

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/altitude-horizon-framework/SKILL.md