agentsclimarketplace

Leadership brief

Skill taufiqigalih/launch-decision-kit/skills/leadership-brief

Decision records, templates, and practice scenarios for the call behind a release, launch, or production milestone — captured before the outcome is known, closed out after it is.

Install
npx -y skills add taufiqigalih/launch-decision-kit --skill leadership-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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).

SKILL.md

3.5 KB, 659 tokens by cl100k_base, as published. Nobody here has run it

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

  1. State the current state in plain terms first, no framing, no lead-in. What's true right now.

  2. 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.

  3. List only action already taken, not action that's planned or hoped for. Planned action belongs in the recovery-option field, not here.

  4. 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.

  5. 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.

  6. 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

  • Every field traces back to the source record — nothing was added for this brief alone.
  • The confidence level on the working diagnosis matches the source, not an upgraded version of it.
  • It's clear whether this brief is reporting a decision or asking for one — never both at once.
  • The recovery trigger named here is the same one in the source record, not a simplified restatement that lost the measurable part.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.