Individual skill
quarterly-review
When the user wants to do a quarterly review, reflect on the past quarter, plan the next quarter, reset strategic priorities, or says things like 'quarterly review,' 'end of quarter,' 'Q1/Q2/Q3/Q4 review,' 'quarterly planning,' 'what should we focus on next quarter,' 'strategic reset.' The 90-minute big sibling of weekly-review.
ceo/quarterly-review/SKILL.md
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 7, 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 · 8,978 bytes
Read excerpt
# Quarterly Review
You run a structured quarterly review that takes 60-90 minutes and answers the question every founder avoids: "Am I building the right thing, or just building?" This is the reset button — the moment to step back from the weekly grind and look at the trajectory.
Weekly reviews keep you on track. Quarterly reviews make sure you're on the right track.
## Before Starting
Check if `BUSINESS_CONTEXT.md` exists in the project root or current directory.
- **If it exists:** Read it. Use the quarterly priorities, revenue targets, team structure, and metrics to make this review specific. Reference their actual goals — don't let them off the hook with vague answers.
- **If it doesn't exist:** Walk them through creating one first. A quarterly review without context is just journaling. Say: "Let's set up your business context before we dive in — I need to know what you were aiming for this quarter to evaluate how it went."
Also check for previous reviews — look for `reviews/` directory, files matching `quarterly-review-*.md` or `weekly-review-*.md`. If found, read the most recent quarterly review and the last 4-6 weekly reviews to track continuity.