Agent skill · writing content · borghei
status-update-generator
Generate weekly executive status updates from Jira/Linear data exports. Produces a structured "highlights / blockers / risks / asks / what's next" briefing in markdown, Confluence, Notion, Linear, JSON, or Mermaid.
Why this skill is useful
Adds a Python script that generates structured executive status updates from Jira/Linear data, which the AI wouldn't reliably create on its own.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Status Update Generator Overview Weekly status updates eat 30-90 minutes of every PM's Friday afternoon and they almost always say the same thing in subtly different ways. This skill standardizes the artifact: pull tickets from Jira or Linear (or any JSON dump), and emit a structured update with five named sections -- Highlights, Blockers, Risks, Asks, What's Next -- plus a traffic-light status (Red / Yellow / Green) for the period. The structure follows SBNR (Status / Blockers / Next / Risks) and a condensed Amazon 6-pager narrative for Highlights; the stoplight verdict follows classic R/Y/G reporting. Core Capabilities Six-section template — Header, Highlights, Blockers, Risks, Asks, What's Next, in a fixed order so exec readers scan in under 5 seconds (full section definitions in references/status-structure-and-workflow.md). Traffic-light discipline — Green / Yellow / Red rules plus anti-patterns (watermelon status, always-yellow, color creep). Multi-format rendering — statusgenerator.py emits all six SHAREDOUTPUTSCHEMA formats: markdown, confluence, notion, linear, json, mermaid. SBNR mapping — compressed async-standup variant mapped to the weekly sections. When to Use Weekly exec status update -- the standard Friday/Monday cadence brief sent to a sponsor, VP, or steering committee. Monthly board / leadership packet -- aggregate four weekly updates into a monthly view. Sprint review summary -- end-of-sprint communication that travels outside the team. Cross-team async standup -- distributed teams where a written async update replaces a sync meeting. Project kickoff status baseline -- the first status update establishes the template and traffic-light baseline. When NOT to use: real-time incident response (use delivery-manager/ incident skills), deep retrospectives (use sprint-retrospective/), or one-to-one stakeholder reporting needing custom framing (use roadmap-communication/). Clarify First Before generating the update, confirm these inputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/status-update-generator