weekly-review-coach

Guide a solo operator through weekly retrospective, OKR check-in, and next-week planning.

6|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/Xipher-Labs/walter-os --skill weekly-review-coach
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review-coach
Source: https://github.com/Xipher-Labs/walter-os/tree/main/skills/weekly-review-coach
Command: npx skills add https://github.com/Xipher-Labs/walter-os --skill weekly-review-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an end-of-week retrospective and OKR check-in into a structured, time-boxed process so you can capture wins, surface blockers, and choose next-week priorities with continuity from last week.

Core Features & Use Cases

  • Structured solo weekly retrospective: Guides you through what went well, what didn’t, and what surprised you without scoring or rewriting your narrative.
  • OKR check-in with visibility: Prompts for current vs target values, red/yellow/green status, and the top blocker per KR, producing a clear KR status table.
  • Next-week priority planning: Helps you define a coherent top 3 plan and maps priorities against OKR status signals to keep focus aligned.
  • Continuity via private state: Reads the prior week’s review file (if present) from your local operator state to carry forward commitments and KR baselines.

Quick Start

Run the weekly-review-coach skill for your Friday session to complete your retro, OKR check-in, and next-week top 3 priorities, writing the output to your private weekly-reviews state file.

Frequently Asked Questions about weekly-review-coach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structured weekly retrospective and OKR check-in as a solo founder?▼

A weekly retrospective and OKR check-in guides you through wins, blockers, and per-KR current versus target values, then maps next-week priorities to OKR status for aligned planning.

What's the best way to maintain state continuity between weekly reviews?▼

Maintain weekly review continuity by reading the prior week's review file from local operator state, carrying forward commitments and KR baselines into the current Friday retro.

How do I track OKR blockers and status during a Friday retro?▼

Track OKR blockers during a Friday retro by collecting current and target values, assigning red, yellow, or green status per KR, and producing a consolidated KR status table.

Can I plan next-week priorities based on my OKR check-in results?▼

Yes, you can plan next-week priorities by confirming a coherent top three plan and mapping those priorities against OKR status signals to keep focus aligned with objectives.

Does a weekly planning session require previous week state files to work?▼

No, previous week state files are optional; the weekly review coach applies continuity using the prior week's state file when available, but runs without it.

What should a solo operator include in an end-of-week review?▼

An end-of-week review should include what went well, what didn't, what surprised you, a per-KR status table, and three coherent next-week priorities mapped to OKR signals.