# weekly-review.skill.md (sample)

<!--
GUIDANCE: A skill is one repeatable job you've written down once so your AI runs it the same way every
time. Trigger, inputs, steps, output. That's the whole pattern. This sample is a Sunday weekly review.
Read it, then write your own for whatever you do by hand every week.
-->

## Trigger

Runs when I type `weekly` or `review`, or every Sunday at 18:00 if I've set it on a schedule.

<!-- GUIDANCE: Name the exact word you'll type. Vague triggers fire at the wrong time or never. -->

## What it reads

- `/notes/this-week/` (everything I dumped in this week)
- `/calendar/last-7-days.md` and `/calendar/next-7-days.md`
- `last-review.md` (so it knows what I said I'd do)

<!--
GUIDANCE: List the exact files. The skill is only as good as what you point it at. If a folder is empty
that week, the skill should say so, not invent.
-->

## Steps

1. Read last week's review. Pull out the 3 things I said I'd do.
2. Check each one against this week's notes and calendar. Mark it done, moved, or dropped. If dropped, ask me one short question: why.
3. Scan this week's notes for anything that looks unfinished: a promise, an open loop, a name with no reply sent.
4. Pick the single most important thing for next week. Not a list of ten. One, with a reason.
5. Draft 2 or 3 next steps under it. Real verbs, real days. "Email the supplier Tuesday," not "follow up soon."
6. Show me the draft. Wait. Don't file anything until I say go.

<!--
GUIDANCE: Number the steps so the order is fixed. Step 6 matters most: the AI proposes, you approve.
A skill that files things silently is how you lose trust in it by week three.
-->

## Output format

Write it to `reviews/[date]-weekly.md` after I approve, using this shape:

```
# Week of [date]

## What I said I'd do
- [item] -> done / moved / dropped (one line each)

## Open loops I almost missed
- [thing], because [why it matters]

## The one thing for next week
[single focus, one sentence]

### Next steps
- [ ] [action], [day]
- [ ] [action], [day]
```

Keep it under one screen. If the "open loops" section is empty, write "clean week" and move on.

<!--
GUIDANCE: Lock the output shape so every week's file looks the same and you can read them back as a run.
Once this works, copy the file, rename it, and write your own: a morning brief, a call prep, a content
draft. The pattern doesn't change. Only the inputs and the steps do.
-->