Elt weekly brief

ELT weekly brief

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

Inputs

1. 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.
2. The week label, for example Week of 2026-11-02. Default to the Monday of the current week.
3. 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.

Each update uses this shape. Rewrite loose prose into it before compiling, keeping the team's own words and numbers:

# Sales

## Metrics
- New ARR booked: $142k (plan $150k)

## Wins
- Closed the largest mid-market deal of the quarter.

## Risks
- [high] Two enterprise deals slipped on security review.

## Asks
- Decision on a 2-year price lock to unblock them.

Severity tags on risks: [high], [med], [low]. If a team did not tag a risk, propose a tag and mark it (tag suggested).

Steps

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

2. Compile.

   node scripts/compile-brief.mjs updates out/elt-brief.md --week "Week of 2026-11-02" --expect Sales,Marketing,Engineering,Customer\ Success

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

3. Add the top of the page above the compiled sections:

   • Headline: one sentence on the week, for example "Bookings 5% under plan, pipeline strong, on-call staffing is the risk to watch."
   • Three things for the ELT meeting: pick from asks and high risks, and say what decision is needed and from whom.
   • 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).
4. 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.
5. 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.
6. Show the brief and ask what to change before it goes out.

Output format

# ELT weekly brief: Week of 2026-11-02

**Headline:** <one sentence>

**For Monday's ELT:** 1. <decision, owner> 2. <...> 3. <...>

**Patterns:** <one or two lines>

Teams reporting: 3 | Asks: 2 | Risks: 4 | Missing updates: Customer Success

## Asks (need a decision or help this week)
## Risks (highest first)
## Metrics
## Wins
## Gaps to chase

Guardrails

• Never change a team's numbers or soften a risk. Summaries may shorten, never reframe.
• Keep people issues (performance, departures by name, compensation) out of the brief. Say "staffing risk" and suggest the leader raise details 1:1.
• The brief is a draft for the user. Do not post or send it anywhere; the user shares it.
• If two updates contradict each other (different numbers for the same metric), show both and ask which is right.

ELT weekly brief

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

Who it is for

COOs, founders, and chiefs of staff who collect updates from every team each week and spend an hour stitching them together.

Example

Input: one markdown file per team in updates/, each with Metrics, Wins, Risks, and Asks sections. Three samples ship in examples/updates/.

Output (out/elt-brief.md, shortened):

# ELT weekly brief: Week of 2026-11-02

Teams reporting: 3 | Asks: 2 | Risks: 4 | Missing updates: Customer Success

## Asks (need a decision or help this week)

1. **Marketing:** Approve moving $5k from paid social to the customer webinar series.
2. **Sales:** Decision on whether to offer a 2-year price lock to unblock the slipped deals.

## Risks (highest first)

- **Engineering:** [high] On-call is down to 3 people after a departure.
- **Sales:** [high] Two enterprise deals slipped to next quarter on security review.

Claude then adds a one-line headline, the three items for the ELT meeting, and patterns across teams.

What it can access

• Reads team updates in updates/ (and the samples in examples/).
• Writes the brief to out/ and may tidy files in updates/.
• Runs one script, scripts/compile-brief.mjs, which uses only Node built-ins.
• No network, no API keys.

Setup

None. Try it on the samples:

node scripts/compile-brief.mjs examples/updates out/elt-brief.md --week "Week of 2026-11-02"