Writes a structured briefing note for editorial managers or senior leadership on editorial, operational, or strategic issues. Use when you need to present complex information concisely for decision-makers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:management-briefing-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes a clear, structured briefing note for editorial managers, department heads, or senior leadership on a specific editorial, operational, or strategic issue.
Writes a clear, structured briefing note for editorial managers, department heads, or senior leadership on a specific editorial, operational, or strategic issue.
Required:
Optional:
A structured memo, typically 300–600 words. Uses clear section headers: Subject, Summary, Background, Key Facts / Developments, Options (if a decision is required), Recommended Action. No jargon. No bullet points longer than one line. Written in third person or an impersonal register — not "I think" but "The recommendation is." Short paragraphs. Designed to be read in under three minutes.
Subject: A reporter on the investigative team has filed a formal complaint against their direct editor alleging repeated exclusion from story assignments following a disagreement over a source's anonymity. HR has received the complaint and is conducting an initial review. The deputy editor needs to be briefed before a team meeting scheduled for Thursday morning. The deputy editor is not the line manager of either party. No disciplinary action has been taken yet. The newsroom does not yet know about the formal complaint.
Key facts:
Decision needed: Whether to reschedule Thursday's meeting or proceed with both parties present.
BRIEFING NOTE — CONFIDENTIAL
Subject: Formal HR complaint between investigative reporter and editor — guidance required on Thursday team meeting
Summary
A formal HR complaint has been filed by a reporter on the investigative team against their direct editor. HR is conducting an initial review, expected to conclude within two weeks. Both parties are scheduled to attend a team meeting on Thursday morning. A decision is needed on whether to proceed with that meeting as planned.
Background
The complaint arises from a disagreement over source anonymity on an unpublished investigation. The reporter alleges they were subsequently excluded from story assignments. The matter was escalated to HR on Monday. Legal has been notified as a precautionary measure. No disciplinary findings have been made and no action has been taken against either party.
Neither party is aware that the other has been informed of this briefing. The wider team has not been told that a formal complaint has been filed.
Key Facts
Options
Option A — Proceed with meeting as scheduled. This avoids disruption to the team and does not signal that anything has changed. Risk: if the dynamic between the two parties is visibly strained, other team members may notice and speculation may follow before HR has concluded its review.
Option B — Reschedule the meeting. This removes the immediate risk of an uncomfortable or escalating situation. It requires a neutral reason to be communicated to the team. Risk: if rescheduled without explanation, this may prompt questions.
Option C — Proceed with meeting but restructure the agenda to remove any items that require direct collaboration between the two parties. This is the lowest-disruption approach if a full postponement is not possible.
Recommended Action
HR should be consulted before Thursday on whether proceeding with both parties present is consistent with their review process. If HR advises caution, Option B or C is recommended. A decision is needed by end of day Wednesday to allow any rescheduling to be communicated.
Please confirm preferred course of action.
Prepared by: [Name / Role] Date: [Date] Distribution: Deputy Editor only
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsWrites structured internal memos for staff or leadership, translating communications situations into concise documents with context, key messages, and recommended actions.
Use this skill when the user asks to "write an exec summary", "summarize this for leadership", "write a summary for the CEO", "board update summary", "executive brief", "leadership update", "write this for C-level", or needs to communicate a complex situation, decision, or initiative status to senior leadership in a concise, structured format. Do NOT use this skill for full stakeholder updates with multiple audience versions — use stakeholder/audience-tailoring for that.
Writes internal communications: 3P updates, newsletters, FAQs, status reports, incident reports, and leadership updates with type-specific guidelines.