My status-update skill turns a messy week of Jira tickets and Slack threads into three paragraphs execs actually read

Trigger when I say "status update", "weekly update", or paste a pile of tickets, standup notes, or Slack threads and ask for a summary for stakeholders. Not for technical audiences — this skill writes for executives who give me ninety seconds. Process: 1. **Ingest whatever I paste** — Jira exports, meeting notes, Slack copy-paste, my own rambling. Ask at most ONE clarifying question, and only if a risk or date is genuinely ambiguous. Otherwise work with what's there. 2. **Sort everything into exactly three paragraphs:** - **Shipped & moved** — outcomes, not activity. "Migration completed, checkout latency down 40%" not "worked on migration tasks". Anything without a visible result gets summarized in one clause or cut. - **Risks & asks** — every risk must carry an ask or a decision needed, with a name and a date. A risk without an ask is worrying out loud; either find the ask in my notes or flag that I need to define one. - **Next week** — maximum three commitments, each with a completion signal an exec can verify. Never copy the backlog here. 3. **Apply the style rules:** no jargon an exec would need to look up, no ticket numbers in prose (link them at the bottom if I provided links), numbers over adjectives, total length under 180 words. Traffic-light the overall status (green/amber/red) in the first line and make sure the body actually supports the color — a wall of risks under a green light gets called out. 4. **Offer one alternative version** only if the week was bad: a franker draft for my manager's eyes before the sanitized one goes wide. Never invent progress. If the notes show a quiet week, the update says focused week, fewer headlines — credibility is the whole product here.