Hand it the skeleton

Describing a layout is harder than showing one

You want a weekly project update with a specific structure. You could describe it: a heading, then status, then what moved, then what is blocked, then what you need from the reader, then a one-line risk note.

Or you can paste the skeleton and ask for it to be filled:

## [Project] — week ending [date]

**Status:** [green / amber / red, one clause of why]

**Moved this week**
- [thing that is now done, with the consequence]

**Blocked**
- [what is stuck] — [who can unstick it] — [since when]

**Need from you**
- [specific ask, or "nothing this week"]

**Risk to flag:** [one line, or "none"]

Everything ambiguous in the description is settled by the skeleton: the order, the heading levels, the bolding, whether items are sentences or fragments, that “nothing this week” is an acceptable value.

Skeletons are the highest-value-per-second format instruction there is, and they are underused because they feel like more work. They are less work: you write it once and reuse it forever.

The bracket convention

Square brackets with an instruction inside them are read as slots, reliably, without you explaining the convention. Put the rule inside the bracket rather than a placeholder word:

• [green / amber / red, one clause of why] beats [status].
• [specific ask, or "nothing this week"] beats [requests].
• [one line, or "none"] prevents the empty section from being silently deleted.

The last of those is the one people miss. Without an explicit empty value, sections with nothing to say tend to vanish or get padded with something invented. Give every optional slot a legal way to be empty.

Where skeletons work best

Anything recurring. Weekly updates, meeting notes, incident reports, handover documents, job adverts, customer replies. If you write something in the same shape more than twice a month, it wants a skeleton.

Anything somebody else will read at speed. A consistent shape means your reader learns where to look, which is worth more than any individual improvement to the prose.

Anything that will be compared. Ten candidate assessments in the same shape can be read side by side. Ten in different shapes cannot.

Anything with mandatory fields. A skeleton makes an omission visible. A missing paragraph in prose is invisible; a slot filled with nothing is not.

The trap: skeletons plus real thinking

A skeleton is a container, and the previous lessons apply. If the analysis needs working and the skeleton has no room for it, you get slots filled confidently with the first plausible thing.

Two fixes. Either put a thinking slot in the skeleton (**Working:** [how you arrived at the status, deleted before sending]) or ask for the analysis first and the filled skeleton after.

Building the skeleton from a good example

The fastest way to make one is not to design it. Take a document of that type that worked, paste it, and ask:

Turn this into a reusable template. Replace everything specific with a bracketed slot describing what belongs there. Keep the structure, the headings and the tone exactly.

You get a skeleton derived from something that was actually accepted, which encodes decisions you did not know you had made: the order of sections, the fact that the ask comes before the detail, the length of each part.

Then keep it in a file with your examples. A template file and an example file are the two durable assets this course produces.

One honest caution

Structure imposed on a unstructured problem makes bad thinking look tidy. If four of your six slots say “none” every week, the skeleton is the wrong shape and it is generating ceremony. Change it or drop it.

The test is whether a reader ever acts on each slot. Slots nobody has acted on in two months are not structure; they are furniture.

Two skeletons worth having tomorrow

The decision note. What I am deciding: [ ] · Options: [each with its cost] · What I would need to believe for option B: [ ] · Recommendation: [ ] · What would change it: [ ]. That last slot is the one that makes the note honest, and it is the one people leave out.

The handover. What this is: [ ] · Current state: [ ] · What is half-finished: [ ] · Where the files are: [ ] · Who to ask: [ ] · What I would do next: [ ]. Handovers fail on the third and fourth slots, always, and a skeleton is what stops them being skipped by somebody in a hurry on their last day.