agentleFS
peterbamuhigirepeterbamuhigire/business-plan-skills/skills/meta-strategy/meta-quarterly-gameplan/SKILL.md

meta-quarterly-gameplan

Skill4 starsChanged 19 days agoMITView on GitHub

Use when converting a completed plan into quarterly execution sprints. Use the relevant plan-section skill for section drafting.

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 24 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈24

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this meta-skill to turn annual strategy into focused 90-day execution.

    line 16
  2. Distinctive:

    Use when converting a completed plan into quarterly execution sprints.

    line 20
  3. Distinctive:

    Use when leadership needs a practical 90-day operating plan rather than an annual narrative.

    line 21
  4. Distinctive:

    Use when accountability, cadence, and execution focus have started to drift.

    line 22
  5. Distinctive:

    Do not use before the annual priorities and constraints are clear.

    line 26
  6. Distinctive:

    Do not create a quarterly plan that tries to advance every objective at once.

    line 27
  7. Distinctive:

    Do not treat this as a project list with no success metric or review rhythm.

    line 28
  8. Distinctive:

    Before finalising the objective, map it to the Balanced Scorecard perspective it most directly advances:

    line 112
  9. Distinctive:

    Every quarter should still have one objective, but that objective must be traceable to the annual strategy map.

    line 119
  10. Distinctive:

    Add a mini strategy map for the quarter:

    line 164
  11. Distinctive:

    Select process: Use the process prioritisation matrix (Impact × Implementation feasibility × Current State × Value) to choose which process …

    line 206
  12. Distinctive:

    Map and analyse: Document as-is process, estimate time and cost, apply improvement techniques

    line 208
  13. Distinctive:

    Implement: Use four parallel tracks: change management, testing, communication, training

    line 209
  14. Distinctive:

    Weekly accountability: If it is not in the weekly plan, it does not happen

    line 250
  15. Distinctive:

    Owner for everything: No action item without a name attached

    line 251
  16. Distinctive:

    Ask for: which quarter, annual plan priorities, team capacity, budget

    line 257
  17. Distinctive:

    Create quarter-end review template

    line 263
  18. Distinctive:

    If the quarter includes process redesign or AI enablement, apply question -> delete -> simplify -> accelerate -> automate

    line 264
  19. Distinctive:

    Use a structured Sunday (P)review to maintain momentum (Kagan, 2024):

    line 268
  20. Distinctive:

    When the quarterly objective includes operational improvement or AI enablement, use this order:

    line 276
  21. Distinctive:

    Create a list of 3-5 marketing experiments with expected vs.

    line 288
  22. Distinctive:

    Run each experiment for 30 days

    line 289
  23. Distinctive:

    If the quarter includes a major investment or digital initiative, add a short business-case audit:

    line 295
  24. Distinctive:

    Every action has an owner - no shared ownership

    line 320

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- dual-compat-start -->

Quarterly Game Plan Meta-Skill

Overview

Use this meta-skill to turn annual strategy into focused 90-day execution. It narrows the plan into a quarterly objective, accountable actions, and short-cycle review discipline.

Use When

  • Use when converting a completed plan into quarterly execution sprints.
  • Use when leadership needs a practical 90-day operating plan rather than an annual narrative.
  • Use when accountability, cadence, and execution focus have started to drift.

Do Not Use When

  • Do not use before the annual priorities and constraints are clear.
  • Do not create a quarterly plan that tries to advance every objective at once.
  • Do not treat this as a project list with no success metric or review rhythm.
  • For meta-quarterly-gameplan, route to the relevant plan-section skill instead when the request is section drafting rather than cross-section analysis.

Required Inputs

InputSource / providerRequired?If absent
Quarterly Gameplan brief and decision audienceClient, plan owner, or approved project filesYesStop before making a recommendation; state the missing decision context.
Claims, assumptions, and supporting evidenceSource register, model, research notes, interviews, or operating recordsYesSeparate known facts from assumptions and return a qualified gap list.
Authority and delivery constraintsRequesting owner and repository instructionsYesRemain read-only and produce a draft or review only.
  • Annual plan priorities and current-quarter context
  • Team capacity, resource constraints, and timing assumptions
  • Any scorecards, KPIs, or implementation milestones already defined
  • Operational realities that affect quarterly sequencing

Workflow

  1. Identify the single most important objective for the quarter.
  2. Break that objective into the few accountable actions that matter most.
  3. Sequence work weekly and assign ownership and review checkpoints.
  4. Reconcile the game plan with annual goals, cash limits, and operating constraints.
  5. Define how progress and slippage will be reviewed.
  6. Flag overload, dependency, or priority-conflict risks.

Decision, stop, and recovery controls

  • Decision point: confirm that the requested output is the 90-day gameplan and that the decision concerns which commitments enter the quarter and which are deferred.
  • Stop condition: halt the affected conclusion if required evidence is missing (annual priorities, available capacity, dependencies, and accountable owners) or if the work could lead to this identified risk: loading a quarter with work that exceeds people, cash, or sequence constraints.
  • Recovery: obtain the missing record or reviewer, repeat the affected check, and update the exception record before release.

Quality Bar

  • The quarter has one dominant objective and a manageable action set.
  • Owners, cadence, and success measures are clear.
  • The plan is realistic for the available capacity.
  • Review discipline is built in from the start.

Anti-Patterns

  • Quarterly plans that simply restate the annual plan.
  • Too many priorities and no forcing function.
  • Actions with no owners or no review points.
  • Game plans that ignore cash, staffing, or dependency constraints.
  • Treating a generic quarterly gameplan template as a conclusion. Correction: tie each choice to the named audience, evidence, and operating constraint.
  • Applying the wrong neighbouring route to meta quarterly gameplan. Correction: confirm the decision and route to the named neighbour before analysis.
  • Treating an assumption as verified evidence. Correction: label it, cite its source or owner, and assign a verification action.
  • Recommending action without a decision threshold. Correction: state the measurable acceptance condition and review trigger.
  • Recording an unavailable check as passed. Correction: mark it not assessed and state the consequence for the decision.
  • Mutating or publishing during an analysis-only task. Correction: remain read-only until the owner gives explicit authority.

Outputs

ArtefactConsumerObservable acceptance condition
Quarterly Gameplan deliverableNamed decision-maker or plan authorThe recommended choice, assumptions, countercase, and next action are explicit.
Evidence and exception registerReviewer, funder, board, or implementation ownerEvery load-bearing claim is sourced or labelled as an assumption; missing checks are not shown as passes.
  • A focused 90-day game plan
  • Ownership, review cadence, and success measures
  • Any constraints or dependency risks requiring leadership attention

Transform the annual business plan into focused 90-day execution sprints. Based on Jan B. King's principle that annual plans fail without quarterly translation into concrete action.

When to Use

Invoke to generate the current quarter's game plan. Can be re-invoked each quarter to create the next sprint. Works best with sections 08, 10, and 13 as input.

What to Generate

1. Quarterly Objective

One clear objective for the quarter the single most important outcome:

Q[X] 20XX Objective: [Clear, measurable statement]
Success metric: [How we know we achieved it]
Why this matters now: [Connection to annual plan]

Before finalising the objective, map it to the Balanced Scorecard perspective it most directly advances:

  • Financial
  • Customer / Market
  • Internal Process
  • Learning / Capability

Every quarter should still have one objective, but that objective must be traceable to the annual strategy map.

2. Monthly Breakdown

Month 1: Foundation

  • Key deliverables
  • Resources needed
  • Decision points

Month 2: Execution

  • Key deliverables
  • Milestones to hit
  • Dependencies to resolve

Month 3: Completion & Review

  • Key deliverables
  • Quality checks
  • Preparation for next quarter

3. Weekly Action Plan

WeekKey ActionsOwnerDeliverableDone?
1[Actions][Who][Output][ ]
2[Actions][Who][Output][ ]
...............
12[Actions][Who][Output][ ]

4. Accountability Matrix

Team MemberQuarterly GoalMonthly TargetsWeekly Check-in Day
[Name][Their Q goal][M1/M2/M3 targets][Day]

5. Resource Allocation

Budget for quarter: $X (from annual allocation)
Team capacity: X person-hours available
Key tools/resources needed: [List]
External dependencies: [List with expected delivery dates]

5A. Quarter Strategy Map

Add a mini strategy map for the quarter:

  • capability or system changes required
  • process improvements expected
  • customer or market result targeted
  • financial effect expected

This prevents the quarter from collapsing into a task list with no strategic logic.

6. Quarter-End Review Template

QUARTER [X] REVIEW
==================
Objective: [What we aimed for]
Result: [What we achieved]
Score: [1-10]

What worked:
1. [Success and why]
2. [Success and why]

What didn't work:
1. [Miss and why]
2. [Miss and why]

Key learnings:
1. [Insight]
2. [Insight]

Carry-forward items:
1. [Incomplete item  next quarter]

Next quarter preview:
- Objective: [Draft Q+1 objective]
- Key shift: [What changes based on learnings]

7. Process Improvement Integration

Each quarterly game plan should include at least one process improvement objective using the BPI methodology (Page, 2015):

  1. Select process Use the process prioritisation matrix (Impact × Implementation feasibility × Current State × Value) to choose which process to improve this quarter
  2. Scope Define boundaries using the 8-section Scope Definition Document (process name, owner, description, scope, responsibilities, client needs, stakeholders, measurements of success)
  3. Map and analyse Document as-is process, estimate time and cost, apply improvement techniques
  4. Implement Use four parallel tracks: change management, testing, communication, training
  5. Measure Compare improved metrics to baseline

Process Prioritisation for Quarterly Focus

Score candidate processes on four weighted criteria (Page, 2015):

CategoryWeightCriteria
Impact~35%Number affected, management level affected
Implementation~30%Time to market, funding required, timing
Current State~20%Customer satisfaction, pain level, process documentation
Value~15%Expected benefit/return

Select the highest-scoring process for this quarter's improvement focus.

8. Transformation Control Points

For larger growth or transformation quarters, review execution through these eight lenses:

  • leadership
  • culture
  • people
  • systems
  • IQ
  • EQ
  • flexibility
  • fearlessness

Turn them into practical review questions:

  • who is leading and deciding?
  • what behaviour change is required?
  • which skills or roles are missing?
  • which systems are constraining progress?
  • what analysis or data is needed?
  • what trust, morale, or stakeholder issue must be managed?
  • where must the plan adapt without losing focus?
  • what bold decision is being avoided?

The King Method: Core Principles

  1. One objective per quarter Focus beats breadth
  2. Weekly accountability If it is not in the weekly plan, it does not happen
  3. Owner for everything No action item without a name attached
  4. Monthly checkpoints Course-correct before it is too late
  5. Honest reviews What did not work matters more than what did

Generation Process

  1. Ask for: which quarter, annual plan priorities, team capacity, budget
  2. Define the single quarterly objective
  3. Break into monthly deliverables
  4. Decompose into weekly action items
  5. Assign ownership for every item
  6. Allocate resources and budget
  7. Create quarter-end review template
  8. If the quarter includes process redesign or AI enablement, apply question -> delete -> simplify -> accelerate -> automate

8. Weekly Accountability System

Use a structured Sunday (P)review to maintain momentum (Kagan, 2024):

  • Every Sunday, 15 minutes: review past week's goals, assess progress, set next week's priorities
  • Send to accountability buddy they must reply AND call out missed commitments
  • Organised by goal categories matching quarterly objectives

9. Algorithm-Based Improvement Sequence

When the quarterly objective includes operational improvement or AI enablement, use this order:

  1. Question the requirement
  2. Delete unnecessary steps
  3. Simplify and optimise
  4. Accelerate cycle time
  5. Automate last

10. Marketing Experiment Cycles

Each quarter should include at least one marketing experiment cycle (Kagan, 2024):

  1. Create a list of 3-5 marketing experiments with expected vs. actual sales
  2. Run each experiment for 30 days
  3. At month-end: double down on what works, kill what doesn't
  4. Carry the winning experiments into the next month

11. Benefits-Realisation Check

If the quarter includes a major investment or digital initiative, add a short business-case audit:

  • what benefit was expected this quarter
  • what actually happened
  • what assumption broke or held
  • what decision follows: continue, fix, rescope, or stop

12. Scorecard Review Gate

At the end of every month, classify the quarter by Balanced Scorecard status:

  • Green - objective and leading indicators on track
  • Amber - one major leading indicator off track; corrective action required
  • Red - objective at risk; trigger a replanning session within five working days

Review both:

  • lagging outcomes achieved so far
  • leading indicators that predict whether the quarter will still land

Quality Criteria

  • Quarterly objective is singular and measurable
  • Quarterly objective is linked to a scorecard perspective and strategy map
  • Weekly actions are specific enough to execute (not "work on marketing")
  • Every action has an owner - no shared ownership
  • Resource requirements are realistic for team capacity
  • Review template is honest captures failures, not just successes
  • Weekly accountability system is in place (Sunday reviews with buddy)
  • Quarterly plan identifies the real execution constraint, not just the activity list
  • Process-improvement quarters follow question -> delete -> simplify -> accelerate -> automate
  • Material initiatives include a benefits-realisation review rather than assuming progress from activity alone

References

  • KPI dashboard and control plan — read when setting the quarter's one metric that matters, guard-rails, lines in the sand, control table and weekly war-room cadence.
  • references/quarterly-strategy-map.md - quarterly objective selection, strategy-map linkage, KPI-cascade design, and review-gate logic based on Balanced Scorecard practice

Evidence Produced

EvidenceFormatAcceptance condition
90-day gameplan decision traceSources, calculations, assumptions, countercase, and selected actionA reviewer can trace the selected action and rejected alternatives to the cited inputs.
Exception recordFailed and not-assessed checks with owner and due actionThe register exposes every unresolved exception that could lead to loading a quarter with work that exceeds people, cash, or sequence constraints.

Capability and Permission Boundaries

Read supplied records and use non-mutating checks to produce the 90-day gameplan; updating the approved action register is permitted when requested. Do not publish, contact third parties, alter live systems, commit funds, or claim legal, tax, audit, valuation, ESG, or investment assurance without the owner's explicit authorisation and the appropriate reviewer.

Degraded Mode

If annual priorities, available capacity, dependencies, and accountable owners cannot be obtained, return a qualified 90-day gameplan covering only the checks that remain supportable. Leave this decision unresolved: which commitments enter the quarter and which are deferred. Record the evidence owner and next check; an inaccessible source, tool, or reviewer is never a pass.

Decision Rules

Decision conditionActionFailure or risk avoided
Evidence is sufficient to decide: which commitments enter the quarter and which are deferredRecord the conclusion, source trail, owner, and review trigger in the 90-day gameplan.Risk of loading a quarter with work that exceeds people, cash, or sequence constraints
Material evidence conflicts or remains uncertainCapacity-check competing commitments by owner, dependency, and cash week; defer the lower-value work rather than overloading the quarter.Selecting an option without resolving the decision-relevant uncertainty
Required evidence is missing: annual priorities, available capacity, dependencies, and accountable ownersMark the decision on which commitments enter the quarter and which are deferred not assessed in the 90-day gameplan, and send it to the quarter owner and executive sponsor.Otherwise, the work risks loading a quarter with work that exceeds people, cash, or sequence constraints

Quality Standards

Accept the 90-day gameplan only when evidence is sufficient for this decision: which commitments enter the quarter and which are deferred. Assumptions and countercases remain visible, calculations and cross-references reconcile, and the reviewer can see how the recommendation addresses the risk of loading a quarter with work that exceeds people, cash, or sequence constraints.

Worked Example

A team proposes nine priorities for four people. Capacity and dependency checks retain the three commitments tied to the funding milestone and place the rest in a sequenced backlog.

<!-- dual-compat-end -->

Quarterly learning and living-plan control

Every quarter must contain at least one explicit learning objective when a material assumption remains unvalidated. State the baseline, experiment or operational change, expected signal, guardrail, decision threshold, owner, and evidence location. At quarter end, record whether the result caused the team to continue, revise, pivot, pause, stop, or standardise; do not close the quarter with activity completion alone.

Use the quarter-end gate to reconcile actual results with the business model, cash plan, KPI dashboard, risk register, stakeholder feedback, and capacity. If evidence invalidates a strategic assumption, update the living plan and sequence rather than forcing the old target. Trigger an early plan refresh when funding, leadership, regulation, customer/beneficiary need, capacity, performance, or stakeholder confidence changes materially. Protect continuity first, then run the strategic review.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.