Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@opsdesk

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

SkillOtherv1.0.0 (latest)Tested
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: elt-weekly-brief
  3. 3description: Compile every team's weekly update into one ELT brief with asks first, risks ranked, metrics by team, wins, and who has not reported. Use on Monday or Friday when a COO, founder, or chief of staff says "pull together the ELT update", "write the weekly exec brief", "summarize the team updates", or pastes several team updates and wants one page.
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# ELT weekly brief
  8. 8
  9. 9One page the leadership team can read in three minutes. Asks come first because they need a decision; risks next, worst first; then metrics, wins, and gaps. The script does the sorting so nothing gets dropped, and you do the judgment: the headline, the patterns across teams, and what to chase.
  10. 10
  11. 11## Inputs
  12. 12
  13. 131. **One update per team** in `updates/`, one markdown file each (`updates/sales.md`, `updates/engineering.md`). If the user pastes updates into chat or points at a doc, save each team's part to its own file first and say which files you made.
  14. 142. **The week label**, for example `Week of 2026-11-02`. Default to the Monday of the current week.
  15. 153. **The teams you expect** (for example Sales, Marketing, Engineering, Customer Success, Finance, People). Ask once, then remember it in `updates/teams.txt` (one per line) for next week.
  16. 16
  17. 17Each update uses this shape. Rewrite loose prose into it before compiling, keeping the team's own words and numbers:
  18. 18
  19. 19```markdown
  20. 20# Sales
  21. 21
  22. 22## Metrics
  23. 23- New ARR booked: $142k (plan $150k)
  24. 24
  25. 25## Wins
  26. 26- Closed the largest mid-market deal of the quarter.
  27. 27
  28. 28## Risks
  29. 29- [high] Two enterprise deals slipped on security review.
  30. 30
  31. 31## Asks
  32. 32- Decision on a 2-year price lock to unblock them.
  33. 33```
  34. 34
  35. 35Severity tags on risks: `[high]`, `[med]`, `[low]`. If a team did not tag a risk, propose a tag and mark it `(tag suggested)`.
  36. 36
  37. 37## Steps
  38. 38
  39. 391. **Collect and normalize.** One file per team in `updates/`. Keep metrics as reported, always with the plan or last week's number when given. Never invent a number or a target.
  40. 402. **Compile.**
  41. 41
  42. 42 ```bash
  43. 43 node scripts/compile-brief.mjs updates out/elt-brief.md --week "Week of 2026-11-02" --expect Sales,Marketing,Engineering,Customer\ Success
  44. 44 ```
  45. 45
  46. 46 It writes `out/elt-brief.md` and prints counts. Sections it recognizes: Metrics (or KPIs), Wins (or Highlights), Risks (or Blockers, Lowlights), Asks (or Decisions needed). Anything else lands under "Other notes".
  47. 473. **Add the top of the page** above the compiled sections:
  48. 48 - **Headline:** one sentence on the week, for example "Bookings 5% under plan, pipeline strong, on-call staffing is the risk to watch."
  49. 49 - **Three things for the ELT meeting:** pick from asks and high risks, and say what decision is needed and from whom.
  50. 50 - **Cross-team patterns:** the same risk or dependency showing up in two or more updates (for example Sales slipping on security review while Engineering is short on-call).
  51. 514. **Check the numbers.** Flag any metric more than 10% off plan with "off plan" in bold. Flag metrics that changed definition or are missing a plan.
  52. 525. **List gaps to chase:** missing teams and empty sections from the script output. Draft a two-line nudge per missing owner the user can send themselves.
  53. 536. **Show the brief** and ask what to change before it goes out.
  54. 54
  55. 55## Output format
  56. 56
  57. 57```markdown
  58. 58# ELT weekly brief: Week of 2026-11-02
  59. 59
  60. 60**Headline:** <one sentence>
  61. 61
  62. 62**For Monday's ELT:** 1. <decision, owner> 2. <...> 3. <...>
  63. 63
  64. 64**Patterns:** <one or two lines>
  65. 65
  66. 66Teams reporting: 3 | Asks: 2 | Risks: 4 | Missing updates: Customer Success
  67. 67
  68. 68## Asks (need a decision or help this week)
  69. 69## Risks (highest first)
  70. 70## Metrics
  71. 71## Wins
  72. 72## Gaps to chase
  73. 73```
  74. 74
  75. 75## Guardrails
  76. 76
  77. 77- Never change a team's numbers or soften a risk. Summaries may shorten, never reframe.
  78. 78- Keep people issues (performance, departures by name, compensation) out of the brief. Say "staffing risk" and suggest the leader raise details 1:1.
  79. 79- The brief is a draft for the user. Do not post or send it anywhere; the user shares it.
  80. 80- If two updates contradict each other (different numbers for the same metric), show both and ask which is right.
Sign in to comment on a line