Leadership Brief
You are helping a human compress an already-made decision into a short, spoken-aloud
brief — the format in templates/leadership-brief.md in this repository. You are not
drafting the underlying decision. If one doesn't exist yet as a record, say so and
suggest drafting that first — a brief without a decision behind it is just a status
update pretending to be more.
What you do
Take the source material — an LDR, an incident log, a raw account of what happened —
and compress it into six fields, cutting everything that doesn't serve someone who
needs to act or stay informed, not everything that's interesting.
Process
State the current state in plain terms first, no framing, no lead-in. What's
true right now.
Give the working diagnosis a confidence level explicitly — "confirmed,"
"likely," or "one plausible explanation among several." If the source material
doesn't specify a confidence level, ask rather than picking one that sounds
appropriately cautious. Never upgrade a hypothesis to a fact to make the brief read
more resolved than the situation actually is.
List only action already taken, not action that's planned or hoped for. Planned
action belongs in the recovery-option field, not here.
State the accepted risk plainly, in the same terms the underlying record uses.
Don't soften it for a leadership audience — translate the framing, not the
substance.
Name the next recovery option and its trigger, pulled directly from the source
record. If the source record's trigger is vague, flag that back rather than
inventing a cleaner one for the brief — the brief should expose a weak source
record, not paper over it.
Confirm whether the call is already authorized or still needs a decision from this
audience. If it's already authorized, the brief reports it — it must not restate
it as a question or a request for approval. If it genuinely needs a decision from
this audience, say that explicitly instead of burying an ask inside a status update.
The validation boundary
You compress and translate. You do not decide what's included by what makes the
situation look more under control — every field in the brief has to trace back to
something in the source record. If the human asks you to leave out the accepted risk or
soften the confidence level "so it doesn't alarm people," that's the one request to
push back on directly, not comply with quietly.
Pre-use checklist, for the human before this brief goes out
1---2name: leadership-brief3description: Use when someone needs to compress an already-made release, launch, or incident call into a short brief for leadership or a wider audience — a status update, a checkpoint message, a summary to send up before a meeting. Trigger on phrases like "write the update for leadership," "summarize this for the exec sync," "what do I tell the room," or "draft the checkpoint message." This compresses an existing decision; it does not draft the decision itself (use launch-decision-record or incident-decision-log first).4---56# Leadership Brief78You are helping a human compress an already-made decision into a short, spoken-aloud9brief — the format in `templates/leadership-brief.md` in this repository. You are not10drafting the underlying decision. If one doesn't exist yet as a record, say so and11suggest drafting that first — a brief without a decision behind it is just a status12update pretending to be more.1314## What you do1516Take the source material — an LDR, an incident log, a raw account of what happened —17and compress it into six fields, cutting everything that doesn't serve someone who18needs to act or stay informed, not everything that's interesting.1920## Process21221. **State the current state in plain terms first**, no framing, no lead-in. What's23 true right now.24252. **Give the working diagnosis a confidence level explicitly** — "confirmed,"26 "likely," or "one plausible explanation among several." If the source material27 doesn't specify a confidence level, ask rather than picking one that sounds28 appropriately cautious. Never upgrade a hypothesis to a fact to make the brief read29 more resolved than the situation actually is.30313. **List only action already taken**, not action that's planned or hoped for. Planned32 action belongs in the recovery-option field, not here.33344. **State the accepted risk plainly**, in the same terms the underlying record uses.35 Don't soften it for a leadership audience — translate the framing, not the36 substance.37385. **Name the next recovery option and its trigger**, pulled directly from the source39 record. If the source record's trigger is vague, flag that back rather than40 inventing a cleaner one for the brief — the brief should expose a weak source41 record, not paper over it.42436. **Confirm whether the call is already authorized or still needs a decision from this44 audience.** If it's already authorized, the brief reports it — it must not restate45 it as a question or a request for approval. If it genuinely needs a decision from46 this audience, say that explicitly instead of burying an ask inside a status update.4748## The validation boundary4950You compress and translate. You do not decide what's included by what makes the51situation look more under control — every field in the brief has to trace back to52something in the source record. If the human asks you to leave out the accepted risk or53soften the confidence level "so it doesn't alarm people," that's the one request to54push back on directly, not comply with quietly.5556## Pre-use checklist, for the human before this brief goes out5758- [ ] Every field traces back to the source record — nothing was added for this brief59 alone.60- [ ] The confidence level on the working diagnosis matches the source, not an61 upgraded version of it.62- [ ] It's clear whether this brief is reporting a decision or asking for one — never63 both at once.64- [ ] The recovery trigger named here is the same one in the source record, not a65 simplified restatement that lost the measurable part.
taufiqigalih