From strategy-skills
Quarterly strategy check-in triggered by "quarterly review", "quarterly check-in", "quarterly planning", "Q1/Q2/Q3/Q4 planning", "quarter review", "90-day plan", or at the start of a new quarter when strategy files exist. Use this for quarterly strategy check-ins that review the business plan for shifts, update focus areas for the quarter, set quarterly outcomes, and flag pace issues against yearly goals.
How this skill is triggered — by the user, by Claude, or both
Slash command
/strategy-skills:business-quarterlyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review the business plan for major shifts, refine yearly Core Focus into quarterly focus, set SMART quarterly Outcomes mapped to yearly ones, and flag if quarterly pace drifts from yearly targets.
Review the business plan for major shifts, refine yearly Core Focus into quarterly focus, set SMART quarterly Outcomes mapped to yearly ones, and flag if quarterly pace drifts from yearly targets.
./references/file-structure.md and ./references/markdown-templates.mdIf no business-plan.md exists, redirect to business-initial. If no yearly files exist, suggest business-yearly first.
If a prior quarter exists:
Ask: "Since last quarter, has anything fundamentally shifted in your market, your understanding of the problem, or your approach?"
Keep this to 1-2 follow-up questions max unless something major changed. If significant shifts emerge, flag that a full yearly strategy review might be warranted first.
Update the last_reviewed date to today at minimum. Apply any shifts identified in step 4.
Take the yearly Core Focus areas and sharpen them for this quarter.
Ask, one at a time:
Each quarterly focus should be a sharpened, more specific version of a yearly focus—not a new area.
Show the refined quarterly focus areas to the user for approval before proceeding.
Dispatch ./reviewers/review-quarterly.md with the quarterly focus areas for quality check.
Save to strategy/{year}/Q{N}/core-focus.md with the user's approved quarterly focus areas.
For each quarterly focus area, set SMART goals:
Compare quarterly outcome targets against yearly targets.
Flag if:
Example: Yearly goal is 100 customers. Q1 target: 25, actual: 15. Q2-Q4 must cover 85 (≈28 per quarter). Flag: "You're 10 behind from Q1. Should we adjust Q2 to 35 to catch up, spread the gap across remaining quarters, or revise the yearly target?"
Show the quarterly Outcomes with pace check findings to the user for approval.
Save to strategy/{year}/Q{N}/outcomes.md with the user's approved quarterly outcomes.
Suggest scheduling a monthly check-in to break the quarter into monthly execution milestones.
Fast business plan check: This is not a full yearly review—just a "has anything changed?" If yes, dig deeper. If no, move on.
Quarterly focus narrows yearly focus: Refine, don't reinvent. Quarterly focus should be a sharper version of existing yearly focus areas.
Pace tracking is critical: The whole point of quarterly review is to catch drift early and decide whether to catch up, spread the gap, or revise targets.
Carry forward honestly: Incomplete items from last quarter deserve a real decision. Don't ghost them—continue, revise, or drop.
One question at a time: Guide the user through the process step by step. Avoid overwhelming multi-part questions.
Everything chains upward: Quarterly outcomes map to yearly outcomes. Quarterly focus maps to yearly focus. Business plan anchors both. Consistency matters.
npx claudepluginhub mgancita/strategy-skills --plugin strategy-skillsGuides end-to-end quarterly planning: reviews past performance, strategy, capacity; generates themes, OKRs, roadmap commitments, resource allocation, risks. Reads knowledge/ files.
Prepares a QBR presentation with performance retrospective, strategic insights, and forward-looking roadmap using brand context and campaign data.
Use this skill when the user asks to "write OKRs", "structure our OKRs", "help with quarterly goals", "OKR review", "are our OKRs good", "how do I write key results", "our objectives and key results", "check our OKRs", or wants to create, review, or improve their OKR structure. Also use this skill when the user's roadmap items don't clearly connect to stated objectives.