altitude-horizon-framework — Claude Code skill: what it does, install

What altitude-horizon-framework does

Two axes carry the whole model. Altitude is how wide you zoom out, from a single feature up to a product portfolio and its budget. Horizon is how far ahead you look, from the current sprint to an annual planning cycle. The author is blunt that this is no seniority ladder: a PM at PM altitude is doing the job well, while a Director at PM altitude has left the real job undone.

Then come four transition zones: thinking altitude, a persona shift from end users to buyers and stakeholders, recovery from hero syndrome, and creating direction instead of waiting for it. Each zone ships with named failure modes, among them hero syndrome, an allergy to process, people-pleasing leadership and the instant gratification trap. A waiter-versus-restaurant-operator table makes the shift in success metrics concrete.

Nothing to run. It reads in about 10–15 min, has no scripts or dependencies, and produces no artifacts; you get vocabulary for a diagnosis, not an action plan. When you want guided coaching rather than a model to read, the author suggests pairing it with director-readiness-advisor. If direction from above is vague, the framework points you to the Cascading Context Map.