altitude-horizon-framework
by deanpetersaltitude-horizon-framework is a decision-making skill for the PM-to-Director transition. Use it to diagnose altitude and horizon gaps, clarify scope and timing, and apply the Cascading Context Map when strategy is vague. It includes practical install, usage, and example guidance for skill authoring.
This skill scores 79/100, which means it is a solid listing candidate for directory users who want a clear PM-to-Director transition framework rather than a generic leadership prompt. The repository gives enough trigger guidance, scenario framing, and example-driven workflow to support a credible install decision, though it lacks supporting files and broader operational scaffolding.
- Clear triggerability: the frontmatter names specific use cases like PM-to-Director transition diagnosis and vague-strategy context building.
- Strong operational framing: the skill defines two core axes, Altitude and Horizon, and explicitly points to the Cascading Context Map.
- Good install-decision value: the example file shows a realistic enterprise-strategy cascade and anti-pattern contrast.
- No install command, scripts, or support files, so users only get the markdown workflow rather than a packaged toolchain.
- The repository appears focused on one leadership concept area, so it may be narrower than users expecting a broad PM skills library.
Overview of altitude-horizon-framework skill
What altitude-horizon-framework is
altitude-horizon-framework is a decision-making skill for the PM-to-Director transition. It explains two practical lenses: Altitude for how broadly you zoom out, and Horizon for how far ahead you think. If you are evaluating altitude-horizon-framework for Skill Authoring, the main value is not career theory; it is a reusable way to diagnose where thinking breaks down and what kind of context is missing.
Who this skill is for
This altitude-horizon-framework skill fits senior PMs, new Directors, and managers who keep getting stuck in “why isn’t this clicking?” conversations. It is also useful for coaches or AI workflows that need to translate vague strategy into clearer team direction. If you need a lightweight altitude-horizon-framework guide for thinking through scope, timing, and leadership context, this skill is a strong match.
What problem it solves
The skill helps answer three real questions: what changes when someone moves from PM to Director, where friction is coming from, and how to create direction when strategy is vague. The differentiator is the Cascading Context Map, which turns top-level goals into business-unit, product, and team-level context without collapsing into random tactics.
How to Use altitude-horizon-framework skill
Install and first-read workflow
To altitude-horizon-framework install, add the skill from deanpeters/Product-Manager-Skills and then read SKILL.md first. The repository currently has one support file, examples/sample.md, so start there after the main skill file. For most users, the fastest path is: read the concept, inspect the example, then apply the framework to your own situation.
Build a strong prompt input
The altitude-horizon-framework usage pattern works best when you provide: your current role, the transition you are facing, the decision that feels unclear, and the kind of output you want. Weak input says, “Explain this framework.” Strong input says, “I’m a senior PM moving into Director, my team lacks strategy, and I need a context cascade for Q3 priorities.” That level of specificity lets the skill produce useful guidance instead of generic leadership advice.
What to read first in the repo
Read SKILL.md for the core model, then examples/sample.md for a worked example of the Cascading Context Map. If you are adapting the framework for your own workspace, copy the structure, not the wording. The skill is designed to help you reason from company priority down to team accountabilities, so the example is more valuable than a shallow summary.
Practical usage tips
Use the skill when the issue is ambiguity, misaligned scope, or shallow strategic translation. It is less useful for narrow execution tasks or generic management coaching. The best altitude-horizon-framework usage pairs a concrete scenario with a target artifact: a diagnosis, a context map, or a role-transition explanation.
altitude-horizon-framework skill FAQ
Is altitude-horizon-framework only for PMs?
No. The altitude-horizon-framework skill is centered on PM-to-Director movement, but the same altitude-and-horizon model helps anyone translating strategy into operating context. It is most valuable when the problem is not “what should I build?” but “how much context should I carry and how far ahead should I think?”
How is this different from a normal prompt?
A normal prompt may ask for advice once. This skill gives you a stable framework for repeated decisions, especially when you need to diagnose whether the gap is altitude, horizon, or both. That makes it better for recurring leadership conversations than a one-off answer.
Does it work for beginners?
Yes, if the beginner is dealing with a real transition or a real ambiguity problem. It is not a beginner-friendly primer on product management basics; it assumes you can describe your role, your team, and the decision friction you are seeing. If you cannot name those inputs yet, the skill will be less useful.
When should I not use it?
Do not use altitude-horizon-framework for tasks that need detailed execution plans, roadmap estimation, or technical implementation steps. It is strongest for context-setting, role clarity, and strategic translation. If your need is tactical delivery, a different skill or prompt will be a better fit.
How to Improve altitude-horizon-framework skill
Give it a real transition case
The highest-quality altitude-horizon-framework skill outputs come from real situations, not abstract leadership questions. Include your current title, target title, the stakeholder tension, and the vague signal you need to decode. For example: “I’m a PM becoming Director; Sales wants commitments, Product wants discovery, and leadership wants enterprise growth.”
Ask for a specific artifact
Improve results by requesting one concrete output: a context cascade, a diagnosis of the altitude gap, a horizon-gap explanation, or a director-level response draft. If you ask for “help understanding the framework,” you will get theory; if you ask for “map CEO priority to team accountabilities,” you will get something you can use.
Watch for common failure modes
The most common mistake is supplying too little organizational context, which causes the model to stay abstract. Another failure mode is asking the framework to replace judgment; it should clarify thinking, not decide politics for you. A good altitude-horizon-framework guide input separates facts, assumptions, and desired outcome.
Iterate from context to action
Use the first answer to expose missing information, then refine with tighter constraints. If the output is too broad, add the business objective, the audience for the answer, and the decision horizon you care about. If you want better altitude-horizon-framework usage, treat the first draft as a diagnostic layer and the second draft as the practical operating version.