Quarterly Goal Reset

A structured quarterly review skill that evaluates your OKRs (Objectives and Key Results) with honest scoring, identifies what to continue, stop, or start, and produces a clear plan for the next quarter. Works with Notion databases, Google Sheets, or plain local files to maintain goal history across quarters.

Supported Platforms & Integrations

Platform	Setup Method	Auth Type	Notes
Notion	Integration token	OAuth2	Reads and writes OKRs in a dedicated database
Google Sheets	Service account	OAuth2	Tracks quarterly goals with color-coded progress
Todoist	API token	REST API	Pulls task completion data related to key results
Linear / Jira	API token	REST API	Maps project milestones to quarterly objectives
GitHub Projects	API token	REST API	Tracks technical project progress against goals
Local Markdown	File path	None	Simple markdown files in ~/.goals/ directory

When to Use This Skill

• Use this at the end of each quarter (March, June, September, December) to formally assess progress
• Use this when goals set three months ago no longer feel relevant and you need to recalibrate
• Use this when you completed most tasks but are unsure if you actually made meaningful progress
• Use this when you want to separate activity from achievement in your quarterly planning
• Use this when annual goals feel too distant and you need a closer checkpoint for accountability
• Consider alternatives when you need weekly task management — use a weekly review agent instead
• Consider alternatives when you need team-level OKR coordination — this is designed for personal goals

Quick Start

Copy
# ~/.claude/skills/quarterly-goal-reset.yaml
current_quarter: Q1-2026
objectives:
  - title: "Advance engineering career"
    key_results:
      - description: "Complete AWS certification"
        target: 1
        current: 0
        unit: certification
      - description: "Ship 3 major features"
        target: 3
        current: 2
        unit: features
      - description: "Give 1 team tech talk"
        target: 1
        current: 1
        unit: talks
  - title: "Improve physical fitness"
    key_results:
      - description: "Run 150 total miles"
        target: 150
        current: 112
        unit: miles
      - description: "Strength train 36 sessions"
        target: 36
        current: 28
        unit: sessions
scoring_method: percentage
history_file: ~/.goals/quarterly_history.json
output_format: markdown

First Run Example

Copy
claude skill quarterly-goal-reset --quarter Q1-2026

Expected Output

Quarterly Goal Reset — Q1 2026 Review
=======================================

OBJECTIVE 1: Advance Engineering Career
  KR1: Complete AWS certification         0/1   (0%)   MISSED
  KR2: Ship 3 major features              2/3   (67%)  PARTIAL
  KR3: Give 1 team tech talk              1/1   (100%) HIT
  Objective Score: 56% — Needs Improvement

OBJECTIVE 2: Improve Physical Fitness
  KR1: Run 150 total miles               112/150 (75%)  PARTIAL
  KR2: Strength train 36 sessions         28/36  (78%)  PARTIAL
  Objective Score: 76% — Good Progress

OVERALL QUARTER SCORE: 66%

HONEST ASSESSMENT:
  What went well:
    - Tech talk delivered and received positive feedback
    - Consistent strength training despite travel weeks
    - 2 features shipped on time with quality

  What did not go well:
    - AWS cert study abandoned in month 2 (scheduling conflict)
    - Running volume dropped in March (weather + motivation)
    - Third feature pushed to Q2 due to scope creep

  Root causes:
    - Over-committed: 5 key results was too many for this quarter
    - AWS cert had no deadline forcing function
    - Running lacked a race or event to train toward

CONTINUE / STOP / START:
  Continue: Strength training routine, feature shipping cadence
  Stop: Setting certification goals without booking exam dates
  Start: Signing up for a race to create running accountability

Q2 2026 DRAFT OBJECTIVES:
  Obj 1: "Complete AWS cert and ship Q1 carry-over feature"
    KR1: Pass AWS exam by April 30 (exam already scheduled)
    KR2: Ship remaining feature by May 15
    KR3: Mentor one junior engineer on a project

  Obj 2: "Run a half marathon in June"
    KR1: Follow 12-week training plan (adherence > 85%)
    KR2: Complete 200 miles total in Q2
    KR3: Race day finish under 2:00:00

Advanced Configuration

Platform-Specific Setup

Notion OKR Database

Copy
notion:
  enabled: true
  database_id: "your-okr-database-id"
  properties:
    quarter: "Quarter"
    objective: "Objective"
    key_result: "Key Result"
    target: "Target"
    actual: "Actual"
    score: "Score"
    status: "Status"
  create_next_quarter: true

Linear Project Mapping

Copy
linear:
  enabled: true
  api_key: "your-linear-api-key"
  team_id: "your-team-id"
  project_to_kr_mapping:
    "Project Alpha": "Ship 3 major features"
    "Infrastructure": "Reduce deploy time by 50%"
  use_completion_percentage: true

Full Options Reference

Parameter	Type	Default	Description
current_quarter	string	auto-detected	Quarter being reviewed (Q1-Q4 + year)
objectives	list	[]	Objectives with nested key results
scoring_method	string	percentage	percentage or google_style (0.0-1.0)
history_file	string	~/.goals/quarterly_history.json	Path for historical quarter data
output_format	string	terminal	terminal, markdown, notion, or google_sheets
carry_forward	bool	true	Automatically carry incomplete KRs to next quarter
root_cause_analysis	bool	true	Generate analysis of why goals were missed
csss_framework	bool	true	Include Continue/Stop/Start/Stretch analysis
draft_next_quarter	bool	true	Generate draft objectives for upcoming quarter
max_objectives	int	3	Recommended maximum objectives per quarter
max_key_results_per_obj	int	4	Recommended maximum KRs per objective
ambitious_target	float	0.70	Score threshold: below this is a miss, above is acceptable
compare_quarters	bool	true	Show trend across previous quarters

Core Concepts

Concept	Purpose	How It Works
OKR Scoring	Quantifies goal achievement	Each key result scored as percentage of target hit, rolled up to objective level
Carry Forward	Prevents abandoned goals	Incomplete KRs from this quarter offered as candidates for next quarter
Root Cause Analysis	Learns from misses	Identifies systemic reasons for missed goals rather than surface-level blame
Continue/Stop/Start	Actionable reflection	Framework for deciding what habits and approaches to keep, drop, or begin
Ambitious Calibration	Sets healthy expectations	Scoring 70% on ambitious goals is considered good using Google-style OKR methodology

Architecture

Current Quarter OKR Data
        |
        v
+--------------------+
| Progress Scorer    |----> Calculates % completion per KR
+--------------------+
        |
        v
+--------------------+     +--------------------+
| Assessment Engine  |---->| Root Cause Analyzer|
| (hit/partial/miss) |     | (why goals missed) |
+--------------------+     +--------------------+
        |
        v
+--------------------+
| Reflection Module  |----> Continue/Stop/Start framework
+--------------------+
        |
        v
+--------------------+     +--------------------+
| Next Quarter Draft |---->| History Logger     |
| (carry-forward +   |     | (quarterly_history |
|  new objectives)   |     |  .json)            |
+--------------------+     +--------------------+

Workflow Examples

Scenario 1: All Goals Hit

Input: Q4 review with all KRs at 80%+ completion

Processing:
  - Scores all objectives as green (hit)
  - Analyzes whether goals were ambitious enough
  - Compares to previous quarters for difficulty calibration

Output:
  Overall Score: 92% — Excellent quarter
  Note: Last 3 quarters scored 85%+, which may indicate goals
  are not ambitious enough. Consider stretching Q1 targets by
  20% to maintain growth pressure.
  Recommended: Add one "moonshot" KR per objective next quarter.

Scenario 2: Major Life Change Mid-Quarter

Input: Job change in month 2 made original career goals irrelevant

Processing:
  - Detects that career KRs became invalid due to context change
  - Separates pre-change and post-change assessment
  - Adjusts scoring to acknowledge the disruption

Output:
  Career objective marked as CONTEXT CHANGED (not scored)
  Pre-change progress (weeks 1-6): On track for all KRs
  Post-change: New role requires completely different goal set
  Recommendation: Set Q2 career goals specific to new role onboarding
  Personal goals (fitness, learning) scored normally: 72% overall

Scenario 3: Multi-Quarter Trend Review

Input: 4 quarters of history available, running annual review

Processing:
  - Aggregates scores across Q1-Q4
  - Identifies which objectives repeated vs were new
  - Calculates improvement trajectory

Output:
  Annual OKR Trend — 2025:
  Q1: 58% | Q2: 67% | Q3: 74% | Q4: 78%
  Trend: Consistent improvement (+20 points over the year)
  Most improved area: Fitness (from 40% to 85%)
  Most stagnant area: Learning (bounced between 50-60% all year)
  Insight: You consistently under-deliver on certification goals.
  Pattern: Signing up for exams (with deadlines) works better
  than open-ended "study" goals.

Best Practices

1. Limit yourself to 2-3 objectives per quarter — More than three objectives guarantees that at least one gets neglected. Fewer objectives with focused key results produce better outcomes than a long ambitious list.

2. Make key results measurable with numbers — Replace vague goals like "improve fitness" with specific targets like "run 150 miles." If you cannot put a number on it, you cannot score it honestly at the end of the quarter.

3. Score with radical honesty — The point is accuracy, not feeling good. A 40% score on an ambitious objective teaches you more than a 100% score on something easy. Resist the temptation to round up.

4. Book deadlines for carry-forward goals — If a goal is carried to the next quarter, attach a hard deadline immediately. Goals that roll forward without deadlines tend to roll forward indefinitely.

5. Separate effort from results — You may have worked incredibly hard and still missed a KR due to external factors. Acknowledge the effort in your assessment, but score the result. This distinction matters for planning.

Common Issues

1. Goals feel irrelevant by mid-quarter — This usually means the goals were not important enough at the start. Use the quarterly reset to replace them, but note the pattern and set more durable goals next time.

2. Scoring feels demotivating — Switch to Google-style OKR scoring where 70% is considered a success. This reframes partial completion as acceptable and reserves 100% for truly exceptional performance.

3. Too many carry-forward goals accumulate — If more than one goal carries forward, it signals overcommitment. Drop the least important carried goal entirely rather than entering the next quarter already behind.

Privacy & Data Handling

All goal data, scores, and reflections are stored locally in ~/.goals/quarterly_history.json. No personal objectives or career aspirations are transmitted externally. If Notion or Google Sheets integration is enabled, data is written only to your own workspace using your own credentials. Linear and Jira integrations pull project data to your local machine only — no goal data is written back to those platforms. You retain full control of your goal history and can delete it at any time by removing the ~/.goals/ directory.