Made by@opsdeskElt weekly brief
@opsdesk/elt-weekly-brief
Turn each team's weekly update into one ELT brief: asks that need a decision first, risks ranked by severity, metrics by team, wins, and a list of who has not reported yet.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# ELT weekly brief
- 3Turns each team's weekly update into one page for the leadership team. Asks that need a decision come first, risks are ranked by severity, and teams that have not reported are listed so you can chase them.
- 5## Who it is for
- 7COOs, founders, and chiefs of staff who collect updates from every team each week and spend an hour stitching them together.
- 9## Example
- 11Input: one markdown file per team in `updates/`, each with Metrics, Wins, Risks, and Asks sections. Three samples ship in `examples/updates/`.
- 13Output (`out/elt-brief.md`, shortened):
- 15```markdown
- 16# ELT weekly brief: Week of 2026-11-02
- 18Teams reporting: 3 | Asks: 2 | Risks: 4 | Missing updates: Customer Success
- 20## Asks (need a decision or help this week)
- 221. **Marketing:** Approve moving $5k from paid social to the customer webinar series.
- 232. **Sales:** Decision on whether to offer a 2-year price lock to unblock the slipped deals.
- 25## Risks (highest first)
- 27- **Engineering:** [high] On-call is down to 3 people after a departure.
- 28- **Sales:** [high] Two enterprise deals slipped to next quarter on security review.
- 29```
- 31Claude then adds a one-line headline, the three items for the ELT meeting, and patterns across teams.
- 33## What it can access
- 35- Reads team updates in `updates/` (and the samples in `examples/`).
- 36- Writes the brief to `out/` and may tidy files in `updates/`.
- 37- Runs one script, `scripts/compile-brief.mjs`, which uses only Node built-ins.
- 38- No network, no API keys.
- 40## Setup
- 42None. Try it on the samples:
- 44```bash
- 45node scripts/compile-brief.mjs examples/updates out/elt-brief.md --week "Week of 2026-11-02"
- 46```