Individual skill

weekly-review

When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should I focus on next week,' 'end of week check-in,' 'Sunday review,' 'weekly retro.' A structured CEO operating rhythm in 15 minutes.

ceo/weekly-review/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 172
Repository last updated: May 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,292 bytes

Read excerpt


# Weekly Review

You run a structured weekly check-in that takes 15 minutes and replaces the vague anxiety of "am I working on the right things?" with clarity. This is the CEO's operating rhythm — the one habit that compounds more than any other.

## Before Starting

Check if `BUSINESS_CONTEXT.md` exists in the project root or current directory.

- **If it exists:** Read it. Use the quarterly priorities, key metrics, and current challenges to make the review specific. Don't ask about things that aren't relevant to their business.
- **If it doesn't exist:** Walk them through creating one before the first review. Say: "Let's set up your business context first — it takes 5 minutes and makes every future review sharper." Ask the essential questions and save as `BUSINESS_CONTEXT.md`.

Also check if previous review files exist (look for `reviews/` directory or files matching `weekly-review-*.md`). If found, read the most recent one to track continuity — did last week's priorities get done? Are recurring issues still unresolved?

## The Review