weekly-review

name	weekly-review
description	The weekly snapshot - gather evidence (dailies, git commits, ship log), update the quarterly scorecard, capture accomplishments and energy, plan next week. Triggers on - weekly review, weekly snapshot, plan my week, review my week, close the week, new week, how was my week.

Weekly review

The glue between the quarterly plan and the daily work. 15-20 minutes, evidence first. Without this ritual the quarter plan is just a wish; say that once if the user skips two weeks.

Step 1: gather evidence (you, before asking anything)

• This week's daily logs in daily/ (wins, log lines, TILs)
• Git commits: for each active project in projects/ with a local repo path, run git log --oneline --since="7 days ago" (and check the system's own repo). Commits are accomplishments the user forgot.
• Ship log and badges in learn/progress.md, new wiki pages, new files in content/published/
• _ops/this-week.md: what was planned
• The current quarter plan at _ops/quarters/YYYY-qN/plan.md, if one exists, plus its latest weekly snapshot

Step 2: the snapshot (with a quarter plan)

Create _ops/quarters/YYYY-qN/weeks/week-NN.md from _templates/weekly-snapshot.md:

1. Focus check: restate the quarterly focus and goal; one honest line: on track, behind, or ahead.
2. Scorecard: carry the items from plan.md, update numerators. Compute the (auto) items from the system (ship log count, published posts, learn level, TILs); ask only for the ones the system cannot see.
3. Accomplished: present the evidence-based list (from step 1) for confirmation; ask what invisible work is missing. Planned-but-not-done gets named, and if the same item slips twice, say so plainly.
4. Top 5 next week: seed from the 12-week plan's next week, adjust to reality. If reality and the plan have diverged for 2+ weeks, suggest "re-plan my quarter" instead of pretending.
5. Wishlist: new shiny ideas that came up go here, not into the week. They get their hearing at the next quarter-plan.
6. Roadblocks, then the energy check, asked as conversation, captured verbatim: what gave energy, what drained it, what should have been a no, what could have been delegated.

Step 3: wire the new week

• Rewrite _ops/this-week.md: the top 5 become the focus (3 starred), leftovers carried with (carried, week N) so chronic carries become visible.
• Update _ops/priorities.md if the standing order changed; real shifts also get a line in _ops/decisions.md.
• Append a one-line week summary to the last daily log of the week.
• End with the new week on one screen. If a scorecard number moved, show it moving: posts 2/12 -> 3/12.

Without a quarter plan

Run the lighter original loop: look back from the dailies, ask "if only one thing ships next week, what is it?", confirm up to 3 focus items, rewrite this-week.md. Then mention once: "when you are ready to aim these weeks at something bigger, say quarter plan."

Rules

• Evidence before questions; never open with "so what did you do this week?" when the system already knows half of it.
• The energy questions are the part users skip and the part that changes behavior; keep them, keep them short.
• Honest beats green: a behind-plan snapshot that says so is a success of the system, not a failure of the user.