Not only at the technical terms MECE, issue tree, problem tree, Minto, Pyramid Principle, SCQA and the McKinsey method, but just as much at how people really say it: where do I start, this problem is too big, I cannot see the wood for the trees, help me break this down, what is the core question, why is our revenue falling, why are customers leaving, and I do not know which data to pull. The frontmatter also states straight away when you should not use it: for pure fact questions with one answer, and for tasks under two hours, because structuring is then more expensive than just doing it.
After that comes a chapter on the theory the skill rests on, and only then the working method: four phases in a fixed order. Phase 1 is the problem definition via SCR, three lines: the situation in facts, the complication that disrupts the situation with since when and how noticeable, and the resolution question. That question becomes the root of the tree, and the instruction is explicit to put it forward for confirmation first, because if the root is wrong, everything beneath it is wasted effort.
Phase 2 is the decomposition. The root question splits into two to five sub-questions, and the skill must deliberately choose a structure from six options: algebraic, process-based, per stakeholder, per segment, following an existing model such as 7S, or internal versus external. Algebraic is preferred where possible, because it is the most watertight. It names which structure it chooses and why, splits at most three levels deep, and tests every split out loud against the two questions from FIG.02.
Phase 3 hangs four things on every branch: a falsifiable hypothesis, an impact estimate of high, medium or low with one sentence why, the evidence needed including where to get it, and an owner who works it out. If the data to estimate the impact is missing, it says [UNKNOWN]. A made-up figure is never filled in there.
Phase 4 closes it off: the MECE check once more, explicit and written out as a sentence rather than a tickbox, the 80/20 marking with a reason, and one concrete action for tomorrow of at most one working day, together with the question it answers and what you know afterwards. There is also a mandatory input checklist of six points, with the rule that the skill only asks about what is missing and asks at most two questions at a time.
It contains a fixed output format with the headings Problem definition, Issue tree, MECE check, 80/20 priority and Action for tomorrow. It contains a fully worked example, which you see in shortened form in FIG.01 and FIG.02. And the file closes with eight refusals, five limits of the framework and six sources. If you want to learn how to write a file like this yourself, writing a SKILL.md NL explains that structure step by step.