weekly-review
walk the week's activity and distill what should graduate to canon
Reads the week's commits, approvals and notes, sorts them into what changed, what was decided and what is open, and proposes the smallest edit that puts each decision in the document it belongs in.
structure generate skill weekly-reviewSkill — weekly-review
Invoke in any agent conversation with /weekly-review. The steps below are a starting opinion, and
they are what runs — edit them until they describe the review this company would actually do on a
Friday.
When to use. Once a week, and before any month where you would otherwise re-decide something you already decided.
Steps.
- Read the week: commits, approved proposals, checkpoints, anything added to
memory/in the last seven days. - Sort it into three piles — what changed, what got decided, what is still open.
- For each decision, ask whether a steering document already says it. If not, name the document it belongs in.
- Propose the smallest edit that would have made this week's confusion unnecessary. One proposal per document; a rewrite is not a review.
- List what the week contradicted — the documents that are now out of date, by path.
- Say what should be deleted or merged. The record earns its keep by staying short.
- Nothing graduates on its own: every proposal waits for a person to approve it.
---
type: skill
name: weekly-review
description: walk the week's activity and distill what should graduate to canon
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---
# Skill — weekly-review
_Invoke in any agent conversation with `/weekly-review`. The steps below are a starting opinion, and
they are what runs — edit them until they describe the review this company would actually do on a
Friday._
**When to use.** Once a week, and before any month where you would otherwise re-decide something you
already decided.
**Steps.**
1. Read the week: commits, approved proposals, checkpoints, anything added to `memory/` in the last
seven days.
2. Sort it into three piles — what changed, what got decided, what is still open.
3. For each decision, ask whether a steering document already says it. If not, name the document it
belongs in.
4. Propose the smallest edit that would have made this week's confusion unnecessary. One proposal
per document; a rewrite is not a review.
5. List what the week contradicted — the documents that are now out of date, by path.
6. Say what should be deleted or merged. The record earns its keep by staying short.
7. Nothing graduates on its own: every proposal waits for a person to approve it.
type: skill
name: weekly-review
about: "Reads the week's commits, approvals and notes, sorts them into what changed, what was decided and what is open, and proposes the smallest edit that puts each decision in the document it belongs in."
version: "0.1.0"