altitude-horizon

Name: altitude-horizon
Author: Productfculty-aipm

70stars33forks

How to install altitude-horizon?

productfculty-aipm/pm-copilot-by-product-faculty/altitude-horizon

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill altitude-horizon

Installs into the current project.

Summary

Use this skill when the user asks about "altitude and horizon framework", "Shreyas Doshi altitude", "working at the right level", "am I too in the weeds", "I'm too tactical", "how do I work at the right altitude", "horizon thinking for PMs", or wants to evaluate whether they're o

Files · 1

View on GitHub

SKILL.md

1	# Altitude and Horizon Framework
2
3	You are applying Shreyas Doshi's altitude-horizon framework to help the PM work at the right level of abstraction for their role and company stage.
4
5	Framework: Shreyas Doshi (3 levels of product work, Lenny's Podcast 2024 + LinkedIn), Jackie Bavaro (PM altitude calibration).
6
7	Key insight: "The biggest growth opportunity for most PMs isn't doing the current level better — it's learning to operate at the next altitude." — Shreyas Doshi
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for the user's role and product stage. Understand: what is their formal scope and what altitude is expected of them?
12
13	## Step 2 — The Altitude Framework
14
15	Altitude describes how abstractly or specifically you're thinking and working:
16
17	High altitude (30,000 feet) — Vision and strategy:
18	- Thinking about: 3-year product vision, strategic positioning, moats, company-level OKRs
19	- Language: "We're trying to make [outcome X] possible for [segment Y]"
20	- Works in: Quarterly planning, board conversations, company direction discussions
21	- When too high: Ideas are inspiring but not actionable. Team can't translate vision to sprint work.
22
23	Mid altitude (10,000 feet) — Product strategy and roadmap:
24	- Thinking about: Now/Next/Later, opportunity prioritization, OKR definition, ICP, beachhead
25	- Language: "We should focus on [segment] because [evidence], which means [roadmap implication]"
26	- Works in: Planning meetings, leadership updates, initiative prioritization
27	- When too high for this level: Roadmap items don't connect to specific user problems.
28	- When too low for this level: Roadmap is just a list of tickets.
29
30	Low altitude (1,000 feet) — Feature and execution:
31	- Thinking about: PRD, user stories, acceptance criteria, sprint priorities, metrics
32	- Language: "When a user does [X], the system should [Y], because [user need]"
33	- Works in: Sprint planning, design reviews, engineering conversations
34	- When too low: Getting into implementation details that should be engineering's domain.
35
36	Ground level — Implementation:
37	- Engineering's domain: How to build it, which libraries, architecture choices.
38	- A PM who spends time here is not doing PM work.
39
40	## Step 3 — The Horizon Framework
41
42	Horizon describes how far ahead you're thinking:
43
44	Long horizon (12+ months): Vision, market evolution, competitive dynamics, platform choices
45	Medium horizon (3–12 months): Roadmap, OKRs, product strategy decisions
46	Short horizon (1–12 weeks): Sprint, feature, launch
47	Now horizon (days): Fires, blockers, immediate decisions
48
49	The right horizon depends on role level:
50	- IC PM: primarily short + some medium horizon thinking
51	- Senior PM: medium + some long horizon thinking
52	- Director/VP: medium + long horizon thinking
53	- CPO: long + very long horizon thinking
54
55	## Step 4 — Self-Assessment
56
57	Based on what the user shares about their work, assess:
58
59	Are they working at the right altitude?
60
61	Signs they're too low for their role:
62	- Spending most time in Jira tickets and Sprint Grooming
63	- Getting pulled into decisions that should be engineering's
64	- Writing detailed acceptance criteria for things that don't need a PM
65	- Not having time for strategy or discovery because execution consumes everything
66
67	Signs they're too high for their role:
68	- Making strategic decisions without evidence
69	- Not knowing the details of what users actually do
70	- Disconnected from the day-to-day shipping
71	- Team can't translate their direction into action
72
73	Are they working at the right horizon?
74
75	Signs they're too short-horizon:
76	- Always reacting, never anticipating
77	- Roadmap looks only 1–2 sprints out
78	- No time for discovery because there's always a fire
79
80	Signs they're too long-horizon:
81	- Great vision but messy execution
82	- Team doesn't feel the PM adds value to their daily work
83	- Plans that never connect to things that ship
84
85	## Step 5 — Calibration Advice
86
87	Based on the assessment, advise:
88	- Which altitude to spend more time at, and what that looks like in practice
89	- Which altitude to spend less time at, and how to delegate or deprioritize it
90	- Which horizon to stretch toward, and what first step gets them there
91	- One concrete change to make this week that shifts the pattern
92
93	## Step 6 — Output
94
95	Produce:
96	- Current altitude/horizon assessment with evidence
97	- Target altitude/horizon for their role and stage
98	- The gap between current and target
99	- Three specific behavioral changes that would shift the altitude/horizon calibration
100	- The type of work to do more of vs. less of in the next month

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Altitude and Horizon Framework

You are applying Shreyas Doshi's altitude-horizon framework to help the PM work at the right level of abstraction for their role and company stage.

Framework: Shreyas Doshi (3 levels of product work, Lenny's Podcast 2024 + LinkedIn), Jackie Bavaro (PM altitude calibration).

Key insight: "The biggest growth opportunity for most PMs isn't doing the current level better — it's learning to operate at the next altitude." — Shreyas Doshi

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryPlanning

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

altitude-horizon

70stars33forks

View on GitHub

How to install altitude-horizon?

productfculty-aipm/pm-copilot-by-product-faculty/altitude-horizon

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill altitude-horizon

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Altitude and Horizon Framework
2
3	You are applying Shreyas Doshi's altitude-horizon framework to help the PM work at the right level of abstraction for their role and company stage.
4
5	Framework: Shreyas Doshi (3 levels of product work, Lenny's Podcast 2024 + LinkedIn), Jackie Bavaro (PM altitude calibration).
6
7	Key insight: "The biggest growth opportunity for most PMs isn't doing the current level better — it's learning to operate at the next altitude." — Shreyas Doshi
8
9	## Step 1 — Load Context
10
11	Read `memory/user-profile.md` for the user's role and product stage. Understand: what is their formal scope and what altitude is expected of them?
12
13	## Step 2 — The Altitude Framework
14
15	Altitude describes how abstractly or specifically you're thinking and working:
16
17	High altitude (30,000 feet) — Vision and strategy:
18	- Thinking about: 3-year product vision, strategic positioning, moats, company-level OKRs
19	- Language: "We're trying to make [outcome X] possible for [segment Y]"
20	- Works in: Quarterly planning, board conversations, company direction discussions
21	- When too high: Ideas are inspiring but not actionable. Team can't translate vision to sprint work.
22
23	Mid altitude (10,000 feet) — Product strategy and roadmap:
24	- Thinking about: Now/Next/Later, opportunity prioritization, OKR definition, ICP, beachhead
25	- Language: "We should focus on [segment] because [evidence], which means [roadmap implication]"
26	- Works in: Planning meetings, leadership updates, initiative prioritization
27	- When too high for this level: Roadmap items don't connect to specific user problems.
28	- When too low for this level: Roadmap is just a list of tickets.
29
30	Low altitude (1,000 feet) — Feature and execution:
31	- Thinking about: PRD, user stories, acceptance criteria, sprint priorities, metrics
32	- Language: "When a user does [X], the system should [Y], because [user need]"
33	- Works in: Sprint planning, design reviews, engineering conversations
34	- When too low: Getting into implementation details that should be engineering's domain.
35
36	Ground level — Implementation:
37	- Engineering's domain: How to build it, which libraries, architecture choices.
38	- A PM who spends time here is not doing PM work.
39
40	## Step 3 — The Horizon Framework
41
42	Horizon describes how far ahead you're thinking:
43
44	Long horizon (12+ months): Vision, market evolution, competitive dynamics, platform choices
45	Medium horizon (3–12 months): Roadmap, OKRs, product strategy decisions
46	Short horizon (1–12 weeks): Sprint, feature, launch
47	Now horizon (days): Fires, blockers, immediate decisions
48
49	The right horizon depends on role level:
50	- IC PM: primarily short + some medium horizon thinking
51	- Senior PM: medium + some long horizon thinking
52	- Director/VP: medium + long horizon thinking
53	- CPO: long + very long horizon thinking
54
55	## Step 4 — Self-Assessment
56
57	Based on what the user shares about their work, assess:
58
59	Are they working at the right altitude?
60
61	Signs they're too low for their role:
62	- Spending most time in Jira tickets and Sprint Grooming
63	- Getting pulled into decisions that should be engineering's
64	- Writing detailed acceptance criteria for things that don't need a PM
65	- Not having time for strategy or discovery because execution consumes everything
66
67	Signs they're too high for their role:
68	- Making strategic decisions without evidence
69	- Not knowing the details of what users actually do
70	- Disconnected from the day-to-day shipping
71	- Team can't translate their direction into action
72
73	Are they working at the right horizon?
74
75	Signs they're too short-horizon:
76	- Always reacting, never anticipating
77	- Roadmap looks only 1–2 sprints out
78	- No time for discovery because there's always a fire
79
80	Signs they're too long-horizon:
81	- Great vision but messy execution
82	- Team doesn't feel the PM adds value to their daily work
83	- Plans that never connect to things that ship
84
85	## Step 5 — Calibration Advice
86
87	Based on the assessment, advise:
88	- Which altitude to spend more time at, and what that looks like in practice
89	- Which altitude to spend less time at, and how to delegate or deprioritize it
90	- Which horizon to stretch toward, and what first step gets them there
91	- One concrete change to make this week that shifts the pattern
92
93	## Step 6 — Output
94
95	Produce:
96	- Current altitude/horizon assessment with evidence
97	- Target altitude/horizon for their role and stage
98	- The gap between current and target
99	- Three specific behavioral changes that would shift the altitude/horizon calibration
100	- The type of work to do more of vs. less of in the next month

Productfculty-aipmPublisher · 69 listings

Preview

Productfculty-aipm/PM-Copilot-by-Product-Faculty

# Altitude and Horizon Framework

You are applying Shreyas Doshi's altitude-horizon framework to help the PM work at the right level of abstraction for their role and company stage.

Framework: Shreyas Doshi (3 levels of product work, Lenny's Podcast 2024 + LinkedIn), Jackie Bavaro (PM altitude calibration).

Key insight: "The biggest growth opportunity for most PMs isn't doing the current level better — it's learning to operate at the next altitude." — Shreyas Doshi

RepoProductfculty-aipm/PM-Copilot-by-Product-Faculty

License—

TypeSkills

CategoryPlanning

UpdatedApr 2026

Repo stars70

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type