# Task 3: weekly leadership update

Goal: turn loose notes into a clear weekly update — then make it repeatable. This is the core Cowork pattern: if a task repeats, it becomes a file.

You are the agent. Do the steps below.

## 1. Read context

Read `CLAUDE.md`, `rules/`, then look in `raw/` for input notes. If notes are missing, ask the user to dump rough notes (messy is fine) into `raw/` under headings: meetings, decisions, open questions, actions, risks. Raw input belongs in `raw/` — that's the dumping ground.

## 2. Create log/ — the structure grows here

This is recurring work: not a project (no end state), not a steering doc (changes weekly). It's a log. Create `log/weekly-update/` now — this is the moment the optional folder earns its place. Update the structure section in `CLAUDE.md` to show `log/` as active.

## 3. Draft

Write `log/weekly-update/<YYYY-MM-DD>.md`. Short enough for a busy leader. Use the user's tone.

```markdown
# Weekly update

## Short version       (3-5 sentences)
## What happened
## What matters         (the so-what)
## Decisions needed     (decision, owner, timing)
## Next actions         (action, owner, date)
## Risks or blockers
```

## 4. Sharpen

Remove filler — every line should inform, decide, or move work forward. Then check against `rules/tone-of-voice.md` and flag what sounds unlike the user.

## 5. Turn it into a skill

Write `skills/weekly-update.md` so next week runs with less explanation:

```markdown
# Weekly update

Use when the user asks for a weekly leadership update.

## Process
1. Read CLAUDE.md and rules/.
2. Read this week's notes from raw/.
3. Ask if owners, dates, or decisions are missing.
4. Draft the update, remove filler, check tone.
5. Save log/weekly-update/<YYYY-MM-DD>.md.
6. Clear or archive the used notes from raw/.
```

## Done when

Notes landed in `raw/`, `log/weekly-update/<date>.md` and `skills/weekly-update.md` exist, `CLAUDE.md` shows `log/` as active, and the update has clear decisions and actions.