altitude-horizon-framework

Teach the altitude-horizon mental model and Cascading Context Map for PM-to-Director transitions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill altitude-horizon-framework-locus-taxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/locus-taxy/locus-SD-toolkit/tree/main/skills/altitude-horizon-framework
Command: npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill altitude-horizon-framework-locus-taxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear mental model and actionable framework to help product teams move from PM to Director thinking by widening scope and horizon and by translating strategy into team work via cascading context.

Core Features & Use Cases

  • Altitude — PM vs Director thinking: understand the shift in scope and cross-functional impact.
  • Horizon — time horizon planning: translate quarterly planning into annual strategy and execution.
  • Cascading Context Map — translate top-level strategy into BU/product-level context and team accountabilities.
  • Use cases: senior PM promoted to Director; teams with unclear direction; executives seeking clearer alignment.

Quick Start

Run a Cascading Context Map to translate vague strategy into team-level priorities and accountabilities.

Frequently Asked Questions about altitude-horizon-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transition from PM to Director thinking in product management?

Transitioning from PM to Director thinking requires shifting your scope and cross-functional impact using the altitude mental model, which helps newly promoted leaders widen their strategic perspective beyond individual product execution.

What is a Cascading Context Map for strategic alignment?

A Cascading Context Map is a framework that translates top-level annual strategy into business unit and product-level context, ensuring clear team accountabilities and strategic alignment during cross-functional planning.

How do I translate vague strategy into team-level priorities and accountabilities?

You can translate vague strategy into team-level priorities by running a Cascading Context Map, which breaks down high-level horizon planning into actionable execution items for your product teams.

Can I use this framework for teams lacking clear product direction?

Yes, the altitude-horizon framework is designed for teams with unclear direction, helping senior PMs and executives establish cross-functional alignment by defining time horizons and cascading context.

Does the altitude-horizon framework require any specific software dependencies?

No, the altitude-horizon framework requires no external software dependencies, relying instead on a root SKILL.md file with YAML frontmatter and optional folders for scripts, references, and assets.

What is the best way to shift from quarterly planning to annual product strategy?

The best way to shift from quarterly planning to annual strategy is applying the horizon mental model, which extends time horizons to translate short-term execution into long-term cross-functional planning.