Quarterly Goals Copilot
Goals that survive week three, because something remembers them and asks
The problem
Setting quarterly goals is a solved problem; the [Quarterly OKR Builder](/toolbox/quarterly-okr-builder) writes a tight set in an hour. Keeping them is where quarters die. The goals get written in January energy, referenced twice, and rediscovered in the week-12 panic, at which point the numbers are whatever they are. The missing piece is not better goals; it is the standing check-in nobody on a small team owns: what moved this week, what stalled, and which key result is quietly failing while everyone works hard on something else. This skill installs that owner.
The tool
Once installed, this skill turns your assistant into the keeper of your quarter. Give it the goals once (built with the OKR Builder or pasted from wherever they live), and it runs the cadence: a weekly check-in that takes five minutes of your reporting, a scorecard that shows each key result's trajectory against where week N should be, and the flags that make drift visible in week four instead of week twelve.
The check-ins are built for busy people: it asks, you answer in a few lines, it updates the record and reflects back only what needs attention. Stalled key results get named, with the gap quantified ("KR2 needs 8 new accounts by week 13; you are at 2 in week 6"). Work that keeps getting reported but maps to no goal gets its own flag, because that is either a missing goal or a quarter leaking into busywork, and the skill says which it thinks it is. At quarter's end it produces the retrospective: what hit, what missed and why per your own weekly notes, and what the next quarter's builder session should know.
What's inside
- One-time intake of the quarter's goals, with baselines and weekly trajectories computed
- A five-minute weekly check-in it initiates the structure for
- The scorecard: each key result against its week-N expectation, trend marked
- Drift flags in plain language, with the gap in numbers
- The unmapped-work flag: effort that serves no stated goal, named
- A quarter-end retrospective built from your own check-ins, ready for planning day
How to use it
- 1Click "Install skill" on this page and copy the install prompt.
- 2Paste it into your AI assistant (Claude, ChatGPT, anything that accepts pasted text).
- 3Give it the quarter's goals; if they are vague, it will push them toward measurable before accepting.
- 4Pick a check-in day and honor it; five minutes weekly is the entire cost of the system.
- 5At quarter's end, take the retrospective into your next planning session instead of memory.
Example
A three-person web agency sets a Q4 with three objectives, including "reduce dependence on the anchor client" with a key result of four new retainer clients. Weeks one through five, the check-ins log proposal work. In week six the skill flags: KR at 1 of 4, trajectory needs 1 every 3 weeks, and the last two check-ins reported eleven hours on the anchor client's rush requests, which map to no objective. The owner reads the flag, declines the next rush job, and reallocates Thursday mornings to outreach. The quarter ends at 3 of 4 with the retrospective noting exactly which week the trade-off got made, and the next quarter's goals include a capacity line the last ones lacked.
Pro tip
Answer the weekly check-in honestly on the bad weeks especially; a record with gaps where the hard weeks were produces a retrospective that blames nothing and teaches nothing. And when the unmapped-work flag fires three weeks running on the same activity, stop treating it as noise: either promote it to a real goal or kill it, because it has already voted itself into your quarter.
Related tools
Want this customized and automated for your business?
We take the tools in this toolbox and wire them into your business: your data, your brand voice, running on autopilot.
Talk to Vexlo