Altitude Shifter Skill
The same fact needs different load-bearing details at different altitudes — the board needs the decision and the risk, the engineers need the constraints, the customer needs the benefit, the new hire needs the context everyone else already has. This skill produces all four at once, and shows its work: what changed between versions and why.
What This Skill Produces
- Four versions of the same content, each complete at its altitude
- The delta table — what was cut, added, and reframed per altitude
- A leakage check — jargon, blame, or bad news that shifted dishonestly between altitudes
Required Inputs
Ask for these if not provided:
- The content — the memo, update, decision, or announcement to shift (paste it)
- What actually happened (if the content is spin-adjacent, the underlying facts — the shifter needs the truth to keep versions consistent)
- Which altitudes are needed (default: all four)
- Anything confidential that must not leak downhill (names, numbers, legal exposure)
Framework: The Four Altitudes
| Altitude |
Load-bearing content |
Length discipline |
The test |
| The board |
The decision, the risk, the ask, the number |
≤5 sentences |
Could they act on this alone? |
| The engineers |
Constraints, interfaces, what is NOT changing, why the deadline is real |
As long as needed, no shorter |
Could they start without a meeting? |
| A customer |
The benefit in their vocabulary; zero internal jargon or org chart |
3–6 sentences |
Would they forward it? |
| The new hire |
The context everyone's assuming — history, acronyms expanded, who owns what |
Generous |
Do they know why, not just what? |
Consistency rule: all four versions must be true simultaneously. Different emphasis is the point; different facts is lying.
Output Format
[Title], at Four Altitudes
🏛 Board
⚙️ Engineering
👤 Customer
🌱 New hire
Delta Table
| Altitude |
Cut |
Added |
Reframed |
Leakage Check
[Jargon that survived into the customer version · bad news that softened on the way up · internal blame that leaked down — each with the fix applied.]
Quality Checks
Anti-Patterns
1---2name: altitude-shifter3description: Re-pitch one piece of content for four audiences — the board, the engineers, a customer, a new hire — with a delta table showing what changed between altitudes and why. Use when asked to rewrite this for execs, explain this to the team, make this customer-facing, or say this four ways. Produces the four versions plus the delta table of what was cut, added, and reframed per altitude.4---5
6# Altitude Shifter Skill
7
8The same fact needs different load-bearing details at different altitudes — the board needs the decision and the risk, the engineers need the constraints, the customer needs the benefit, the new hire needs the context everyone else already has. This skill produces all four at once, and shows its work: what changed between versions and why.
9
10## What This Skill Produces
11
12- **Four versions** of the same content, each complete at its altitude
13- **The delta table** — what was cut, added, and reframed per altitude
14- **A leakage check** — jargon, blame, or bad news that shifted dishonestly between altitudes
15
16## Required Inputs
17
18Ask for these if not provided:
19- **The content** — the memo, update, decision, or announcement to shift (paste it)
20- **What actually happened** (if the content is spin-adjacent, the underlying facts — the shifter needs the truth to keep versions consistent)
21- **Which altitudes are needed** (default: all four)
22- **Anything confidential** that must not leak downhill (names, numbers, legal exposure)
23
24## Framework: The Four Altitudes
25
26| Altitude | Load-bearing content | Length discipline | The test |
27|---|---|---|---|
28| **The board** | The decision, the risk, the ask, the number | ≤5 sentences | Could they act on this alone? |
29| **The engineers** | Constraints, interfaces, what is NOT changing, why the deadline is real | As long as needed, no shorter | Could they start without a meeting? |
30| **A customer** | The benefit in their vocabulary; zero internal jargon or org chart | 3–6 sentences | Would they forward it? |
31| **The new hire** | The context everyone's assuming — history, acronyms expanded, who owns what | Generous | Do they know why, not just what? |
32
33**Consistency rule:** all four versions must be true simultaneously. Different emphasis is the point; different facts is lying.
34
35## Output Format
36
37---
38
39# [Title], at Four Altitudes
40
41## 🏛 Board
42## ⚙️ Engineering
43## 👤 Customer
44## 🌱 New hire
45
46## Delta Table
47| Altitude | Cut | Added | Reframed |
48|---|---|---|---|
49
50## Leakage Check
51[Jargon that survived into the customer version · bad news that softened on the way up · internal blame that leaked down — each with the fix applied.]
52
53---
54
55## Quality Checks
56
57- [ ] Each version passes its altitude test (act / start / forward / understand-why)
58- [ ] All four versions are simultaneously true — no fact contradicts across altitudes
59- [ ] The board version contains the risk, not just the win
60- [ ] The customer version contains zero internal jargon, team names, or process language
61- [ ] The delta table explains reframings, not just lists them
62
63## Anti-Patterns
64
65- [ ] Do not just shorten — each altitude has different load-bearing facts, not fewer of the same ones
66- [ ] Do not leak internal jargon downhill or customer-blame uphill
67- [ ] Do not soften bad news as it goes up — the board version carries the same risk the engineers see
68- [ ] Do not write the new-hire version as a summary — it's the version with MORE context, not less
69- [ ] Do not produce four versions without the delta table — the table is what makes the shift inspectable
Mohit Aggarwal