pm-weekly-reviewlisted

# PM weekly review The end-of-week version of `pm-morning-brief`. Pulls a week's worth of signal and produces a structured retrospective that the user reads in 10 minutes before logging off. Surfaces patterns that don't show up at the daily level: stakeholders the user hasn't talked to in two weeks, decisions that keep getting punted, TODOs that have rotted, projects that lost momentum without anyone naming it. Saves the review to `pm-state/inbox/YYYY-MM-DD-weekly-review.md` so the user can reference it next Monday. ## When to use - Friday afternoon, before logging off - Late on the last working day of a sprint or quarter - Before a quarterly business review or board prep, as a "what happened this quarter" digest Don't use when: - It's earlier in the week (use `pm-morning-brief` instead) - The user is asking about a specific project (run that project's status check directly) - No pm-state exists. Surface that and stop. ## How to apply ### 1. Chain to `pm-context-loader` Load `you.md`, the project list, cross-project stakeholders. ### 2. Pull the week's calendar The last 7 days of calendar entries. For each meeting, identify: - Whether it happened (cancelled meetings count differently) - Whether it had a Granola transcript - Whether the transcript got a debrief (cross-reference `pm-meeting-debrief` history) Flag meetings that happened but never got debriefed — those are likely sources of uncaptured commitments. ### 3. Pull the week's transcripts Use the Granola