Use the pyramid-principle skill whenever you write executive-facing prose; it pays for itself there and nowhere else.
Situation. You write memos, docs, PR descriptions, reports - things a busy reader must grasp fast.
Complication. LLMs (and most writers) default to context-first: setup, reasoning, conclusion buried last. Reader hits paragraph 4 before the point. "Be concise" and "be MECE" don't fix it - vague advice doesn't change model behavior.
Question. Is a structured skill worth the overhead over just writing?
Answer. Yes for executive writing, no for casual chat or code - three reasons below.
The skill forces BLUF - bottom line up front. Answer in the first sentence, support next, data last. Directly counters the context-first default that pushes the conclusion to the bottom where readers never reach it.
"Lead with the answer" appears to fight "think before you commit." The skill resolves the conflict: reason bottom-up in a hidden scratchpad, then emit top-down. Accuracy lives in the reasoning (cited tests: reasoning-first ~47% vs answer-first ~33%); pyramid structure lives in the output. Without the split, leading with the answer turns reasoning into post-hoc rationalization.
Vague directives ("be concise," "be MECE") don't move an LLM. The skill swaps them for enumerated, affirmative rules: one bottom-line sentence, three support arguments, named dimensions instead of the word "MECE," positive phrasing over prohibitions (models read negation poorly). Plus two cheap pre-send checks - first-sentence test, read-titles test - that catch a buried lead before shipping.
The structure earns its overhead only when a reader must extract an argument fast. On a one-line answer or a code edit, the scaffolding is pure cost.
Bottom line: worth it when output is executive-facing writing and the reader needs the argument in 30 seconds; skip it everywhere else.