---
name: weekly-update
description: Writes the weekly status update from this week's notes, following the house format of wins, risks, and asks. Use when the user says "write the weekly update", "draft my status note", "what do I send the team this week", or asks for a summary of the week's progress. SKIP for a one-off summary of a single document, and for anything that gets sent without the user reading it first.
---

# Weekly update

## Before you start

Read `CLAUDE.md` for the vocabulary. If the notes folder is empty or covers a
different week than the user asked for, say so and stop. Do not invent progress.

## Steps

1. Gather every note file changed in the last seven days.
2. Sort what you find into three buckets, and only these three:
   - **Wins**: things that finished. Not things that progressed.
   - **Risks**: things that could stop a win from happening. Each one needs a
     named owner or it is not a risk, it is a worry.
   - **Asks**: decisions or approvals needed from someone else, each with the
     name of the person and the date it is needed by.
3. Anything that fits none of the three buckets gets left out. A weekly update is
   not a diary.
4. Write it in the format below. Six bullets maximum in total. If there are more
   than six, the extra ones were not important enough for this update.
5. Show it to the user. Never send anything.

## Format

```
Week of [date]

Wins
- [what finished, and why it mattered]

Risks
- [what could go wrong] (owner: [name])

Asks
- [what you need] from [name], by [date]
```

## Rules

- Plain language. If a sentence needs a glossary, rewrite the sentence.
- Every claim traces to a note. If you cannot point at the note, cut the line.
- No filler. "Continued work on X" is not a win and does not go in.
- If a week genuinely had no wins, say that. A short honest update is worth more
  than a padded one, and padding is what teaches people to stop reading these.

---

## How to adapt this

Three things make a skill fire at the right moment and stay useful:

1. **The description at the top is the whole selection mechanism.** Claude reads
   only the name and description when deciding whether to use this. It has not
   read a word of the body. Write the description in third person, say what the
   skill does AND when to use it, and include the actual phrases you would type.
2. **The SKIP line matters as much as the trigger.** It is how you stop three
   similar skills from all looking equally plausible.
3. **Keep the body short and the steps specific.** This is a procedure, not an
   essay. The more exact the sequence, the more consistent the result.