Agent skill

Quarterly Review

by TheCraigHewitt in TheCraigHewitt/skills

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…

MITAuto-check passedKnowledge Management

Install Quarterly Review

skills CLI
$ npx skills add TheCraigHewitt/skills --skill quarterly-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills quarterly-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ceo/quarterly-review .claude/skills/quarterly-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quarterly-review
GitHub stars
159
Token cost
~2.2k tokens
SKILL.md length
1,101 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 8 steps: Quarter Scorecard (15 minutes) → Revenue & Growth Review (10 minutes) → What Worked (10 minutes) → …
  • Wants to do a quarterly review
  • SKILL.md covers Before Starting, The Review, Output and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quarterly Review is an agent skill from TheCraigHewitt/skills. 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.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Journaling and reflection and Product roadmapping. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to do a quarterly review
  • Reflect on the past quarter
  • Plan the next quarter
  • Reset strategic priorities

Example prompts

  • “quarterly review,”
  • “end of quarter,”
  • “Q1/Q2/Q3/Q4 review,”
  • “/quarterly-review”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Quarter Scorecard (15 minutes)
  2. Revenue & Growth Review (10 minutes)
  3. What Worked (10 minutes)
  4. What Didn't Work (10 minutes)
  5. Strategic Priority Assessment (15 minutes)
  6. Team & Capacity Review (10 minutes)
  7. Next Quarter's Big Bets (15 minutes)
  8. Annual Goal Check-In (5 minutes)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quarterly Review loads about 2.2k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 1,101 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 1,101 words, ~2,233 tokens.

Download SKILL.mdSave it as .claude/skills/quarterly-review/SKILL.md (or your agent's skills folder).
name
quarterly-review
description
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.

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.

The Review

Run through these sections in order. This is a conversation, not a form — ask follow-up questions, push back on vague answers, and don't let them skim past the hard parts.

1. Quarter Scorecard (15 minutes)

Start here: "What were your 3-5 goals for this quarter, and how did you do against each one?"

For each goal:

  • What was the target?
  • What actually happened?
  • Hit / Missed / Partially hit?
  • If missed: was the goal wrong, the execution wrong, or did circumstances change?

Then the key metrics:

MetricStart of QuarterEnd of QuarterTargetHit?

If they don't have clear quarterly goals, that's the first finding. Flag it: "Not having defined quarterly goals means you can't tell if you won or lost. Let's fix that for next quarter."

2. Revenue & Growth Review (10 minutes)

Ask for the numbers:

  • Revenue at start of quarter vs end
  • Growth rate (MoM or QoQ)
  • Trajectory: accelerating, flat, or decelerating?
  • Cash position and runway (if relevant)
  • New revenue vs expansion vs churn

The question that matters: "If this trajectory continues for 4 more quarters, where do you land? Is that where you want to be?"

If the answer is no, that's a strategic problem, not a tactics problem. Flag it for the priority-setting section.

3. What Worked (10 minutes)

Ask: "What were the 2-3 biggest wins this quarter? What actually moved the needle?"

For each win:

  • Why did it work?
  • Was it repeatable or a one-time event?
  • Are you doubling down on it next quarter?

Then: "What surprised you — something that worked better than expected?"

Surprises often reveal opportunities you're not investing in enough.

4. What Didn't Work (10 minutes)

Ask: "What were the 2-3 biggest misses or disappointments?"

For each:

  • What happened?
  • Was the idea wrong, the execution wrong, or the timing wrong?
  • What did you learn?
  • Are you trying again, pivoting, or killing it?

Then the harder question: "What did you avoid doing this quarter that you knew you should have done?"

Most founders have at least one. Name it. Avoidance compounds.

5. Strategic Priority Assessment (15 minutes)

This is the core of the quarterly review. Go through every major initiative or priority and sort into three buckets:

Keep — It's working. Continue or accelerate. Kill — It's not working, or it's not worth the opportunity cost. Stop. Start — Something new that the quarter's data suggests you should begin.

For each item, ask:

  • Is this still the highest-leverage use of your time and resources?
  • If you started this company today and knew what you know now, would you still do this?
  • What's the opportunity cost of continuing?

Push back on the instinct to keep everything. Founders are bad at killing things. "You can't add a priority without removing one. What comes off the list?"

Show full SKILL.md (458 more words)Show less
6. Team & Capacity Review (10 minutes)

Ask:

  • "Is your team right for where you're going next quarter?"
  • Who exceeded expectations?
  • Who's struggling, and do they need coaching or a role change?
  • Any hires you need to make? Any you've been avoiding?
  • Are you the bottleneck anywhere? (Be honest.)
  • How's the team's energy and morale?

If they're a solo founder or very small team: "Are you doing work that you should be hiring for or delegating?"

7. Next Quarter's Big Bets (15 minutes)

Now look forward. Based on everything above:

"What are your 3 big bets for next quarter?"

Three. Not five, not seven. Three things that, if they go well, make it a great quarter.

For each:

  • What does success look like? (Specific, measurable)
  • What's the first action in week 1?
  • What could derail it?
  • What resources does it require?

Then: "If you could only accomplish ONE of these three, which one matters most?"

That's the priority. The other two support it.

8. Annual Goal Check-In (5 minutes)

Zoom out one more level:

  • Where are you vs. your annual goals?
  • Are the annual goals still right, or have circumstances changed?
  • At current trajectory, will you hit them?
  • Any mid-year corrections needed?

If they don't have annual goals, suggest setting them now — even rough ones. "What does December look like if this year goes well?"

Output

Generate a structured quarterly review document:

markdown
# Quarterly Review — [Quarter] [Year]

**Reviewed:** [Date]
**Quarter:** [Start date] - [End date]

## Scorecard
| Goal | Target | Actual | Status |
|------|--------|--------|--------|
| [Goal 1] | [Target] | [Actual] | Hit / Missed / Partial |

## Key Metrics
| Metric | Start of Q | End of Q | Change | On Track? |
|--------|-----------|----------|--------|-----------|

## Revenue & Growth
- Revenue: $[X] → $[Y] ([Z]% growth)
- Trajectory: [Accelerating / Flat / Decelerating]
- Cash position: [if shared]
- Runway: [if relevant]

## What Worked
1. **[Win]** — [Why it worked. Repeatable?]
2. **[Win]** — [Why it worked. Repeatable?]

## What Didn't Work
1. **[Miss]** — [What happened. Lesson learned.]
2. **[Miss]** — [What happened. Lesson learned.]

## What I Avoided
- [The thing they knew they should have done but didn't]

## Strategic Priorities — Keep / Kill / Start
### Keep
- [Priority] — [Why it stays]

### Kill
- [Priority] — [Why it goes]

### Start
- [Priority] — [Why it's new]

## Team Assessment
- [Key observations about team, hires needed, bottlenecks]

## Next Quarter: 3 Big Bets
1. **[Bet 1]** — Success = [definition]. First action: [specific]. Risk: [what could derail it].
2. **[Bet 2]** — Success = [definition]. First action: [specific]. Risk: [what could derail it].
3. **[Bet 3]** — Success = [definition]. First action: [specific]. Risk: [what could derail it].

**#1 priority if forced to choose:** [Which bet matters most]

## Annual Goal Check-In
- [Where they stand vs. annual targets. Any corrections needed.]

## Energy: [X/10]
[How the founder is feeling. What would help.]

Save to reviews/quarterly-review-[YYYY]-Q[N].md.

Rules

  1. This is not a weekly review with bigger numbers. Weekly reviews track execution. Quarterly reviews question the strategy. If you're not asking "should we still be doing this?" you're doing a monthly review, not a quarterly one.
  2. Force the kills. Founders will try to keep everything and add new things. That's how quarters get overloaded. Every new priority requires removing an old one. Hold the line.
  3. Don't let vague goals slide. "Grow revenue" is not a goal. "$50K MRR by end of Q2" is a goal. Push for specificity — it's the only way to evaluate next quarter.
  4. Name the avoidance. The most valuable part of a quarterly review is often the thing they've been avoiding. It might be a hard conversation, a failing product, a hire they need to make, or a partnership they need to end. Name it.
  5. Three bets, not five. Constraint creates clarity. If everything is a priority, nothing is.
  6. Connect the quarters. If this isn't their first review, reference the last one. Did the bets pay off? Are the same problems recurring? Patterns across quarters reveal strategic issues that weekly data can't show.
  7. End with energy. Same as weekly review, but higher stakes. A founder who's exhausted going into a new quarter won't execute well no matter how good the plan is.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ceo/quarterly-review of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Quarterly Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quarterly Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quarterly Review this skillTheCraigHewitt/skills159—~2.2kAutomated safety check: PassMIT
Weekly Reviewandreaskelm/pm-brain234—~1.4kAutomated safety check: PassCustom licence
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Munger Perspectivealchaincyf/munger-skill3791 repos~3.7kAutomated safety check: PassMIT
Daily Journalhuytieu/COG-second-brain1.3k—~1.3kAutomated safety check: PassMIT
Letterboxd Diaryjoe-bell/skills211—~4.2kAutomated safety check: PassMIT

Similar skills

  • Weekly Review

    andreaskelm/pm-brain

    Plan or close the week using PM cadence rituals, draft the weekly note (YYYY-Www.md), resolve due decisions, and run the Friday drift sweep across decisions, live assumptions, initiatives, and…

    234 GitHub stars~1.4k tokensUpdated 2 days ago
    Knowledge ManagementAuto-check passed
  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed
  • Munger Perspective

    alchaincyf/munger-skill

    查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研, 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。

    379 GitHub starsUsed in 1 repo~3.7k tokens
    Knowledge ManagementAuto-check passed
  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 9 days ago
    Knowledge ManagementAuto-check passed
  • Letterboxd Diary

    joe-bell/skills

    Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.

    211 GitHub stars~4.2k tokensUpdated 4 days ago
    Knowledge ManagementAuto-check passed
  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Quarterly Review

What does Quarterly Review do?

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…. Quarterly Review is an agent skill from TheCraigHewitt/skills.' The 90-minute big sibling of weekly-review.

When should I use Quarterly Review?

Quarterly Review fits situations like: wants to do a quarterly review; reflect on the past quarter; plan the next quarter; reset strategic priorities.

How do I install Quarterly Review in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill quarterly-review -a claude-code`. Or copy the skill folder (ceo/quarterly-review in TheCraigHewitt/skills) into .claude/skills/quarterly-review in your project. Claude Code loads it when a task matches its description.

How do I install Quarterly Review in Codex?

Run `npx skills add TheCraigHewitt/skills --skill quarterly-review -a codex`. Or copy the skill folder (ceo/quarterly-review in TheCraigHewitt/skills) into .agents/skills/quarterly-review in your project. Codex loads it when a task matches its description.

Can I use Quarterly Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill quarterly-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quarterly-review, .gemini/skills/quarterly-review, .github/skills/quarterly-review and .opencode/skills/quarterly-review in your project.

What does Quarterly Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Quarterly Review is instructions for the agent only.

Does Quarterly Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quarterly Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quarterly Review use?

Quarterly Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quarterly Review use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quarterly Review?

Skills that share tags, products or a category with Quarterly Review: Weekly Review (andreaskelm/pm-brain, 234 stars), LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 379 stars) and Daily Journal (huytieu/COG-second-brain, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quarterly Review?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.