Weekly Update

# Weekly Update

Turn a list of bullets into a polished weekly update email — the kind
managers and stakeholders actually read.

## When to use

Use this skill when the user:
- Pastes a list of "what I did this week" bullets
- Says "write my weekly update"
- Says "summarize my week for my manager"

## Inputs

Required: a bullet list of accomplishments, blockers, and/or plans for
next week. Order doesn't matter.

Optional:
- `audience` — manager (default), team, exec, customer
- `tone` — direct (default), warm, formal
- `name` — sender's first name for the sign-off

## Output format

```
Subject: Weekly Update — <Week of <date>>

Hi <audience or name>,

<1–2 sentence opening — top headline of the week>

**This week**
- <accomplishment 1, framed for the audience>
- <accomplishment 2>
- <accomplishment 3>

**Blockers / risks**
- <blocker 1, with what would unblock it>

**Next week**
- <plan 1>
- <plan 2>

<Optional: 1 sentence ask if you need a decision>

— <Name>
```

If there are no blockers, replace that section with:
> _No blockers this week._

## Process

1. Cluster the user's bullets into:
   - Shipped / completed (past tense — what happened)
   - Blocked (currently stuck on)
   - Planned (going to do next)
2. For each "shipped" bullet, rewrite from "I did X" to "X is done /
   shipped / live". The reader cares about the outcome, not the verb.
3. Frame for the audience:
   - **Manager**: lead with impact, then status. Never bury a missed deadline.
   - **Exec**: cut detail by half. Outcomes only.
   - **Team**: include detail; cross-team dependencies up front.
   - **Customer**: omit internal jargon entirely.
4. The opening sentence should be the single most important thing that
   happened.
5. Add an explicit ask if the user has one — a decision needed, a sign-off,
   a meeting. Don't bury it.

## Example

**Input bullets:**
- shipped skill import endpoint
- 12 tests, all passing
- review took 2 days because of CI flakiness
- blocked on infra team for new postgres
- next week: ship the marketplace UI

**Output:**
```
Subject: Weekly Update — Week of Mar 10

Hi Priya,

Skill import landed — users can now drop a SKILL.md from paste, URL, or
GitHub and have it on their agent in 60 seconds.

**This week**
- Shipped `POST /api/skills/import` with full test coverage (12 tests)
- Migrated `skill_definitions` to add `sha256`, `source_kind`,
  `version_counter` columns
- Code review finalized; merged to main

**Blockers / risks**
- Postgres upsize for the marketplace is still gated on infra. Filed
  ticket INFRA-241; ping welcome if you can nudge.

**Next week**
- Build the public `/skills` marketplace UI on top of the new endpoint
- Add system-skill seed (10 curated skills)

— Sam
```

## Hard rules

- Subject line: max 60 chars, never clickbait.
- Greeting: match the audience. "Hi team" for a team update; "Hi Priya"
  for a manager.
- Never inflate. "Made progress on X" with no concrete output is a tell.
- Never end with "let me know if you have any questions" — that's filler.
  If you have a question, ask it. Otherwise stop.
- 200 words or fewer for a typical week. Longer = nobody reads it.