Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
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 operating at the right level of abstraction for their role and stage.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:altitude-horizonThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Use this skill when the user is confused about why their execution feels chaotic, when work isn't connecting to outcomes, when they ask "why does everything feel urgent but nothing moves the needle", when they ask about "Shreyas Doshi's framework", "3 levels of product work", "how to think about product strategy vs execution", or when they want to diagnose whether a problem is a strategy problem or an execution problem.
Understand the PM-to-Director transition through altitude and horizon thinking. Diagnoses scope, time-horizon, or leadership-level gaps.
Stakeholder management skill for product managers.
Share bugs, ideas, or general feedback.
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
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?
Altitude describes how abstractly or specifically you're thinking and working:
High altitude (30,000 feet) — Vision and strategy:
Mid altitude (10,000 feet) — Product strategy and roadmap:
Low altitude (1,000 feet) — Feature and execution:
Ground level — Implementation:
Horizon describes how far ahead you're thinking:
Long horizon (12+ months): Vision, market evolution, competitive dynamics, platform choices Medium horizon (3–12 months): Roadmap, OKRs, product strategy decisions Short horizon (1–12 weeks): Sprint, feature, launch Now horizon (days): Fires, blockers, immediate decisions
The right horizon depends on role level:
Based on what the user shares about their work, assess:
Are they working at the right altitude?
Signs they're too low for their role:
Signs they're too high for their role:
Are they working at the right horizon?
Signs they're too short-horizon:
Signs they're too long-horizon:
Based on the assessment, advise:
Produce: