/yearly-planner
Produce the 12-month operational Yearly Planner — the calendar companion to the Growth Plan in Part 8. Translates strategy into month-by-month execution.
$ npx -y skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/yearly-planner
Context preview
The summary Claude sees to decide when to auto-load this skill.
Produce the 12-month operational Yearly Planner — the calendar companion to the Growth Plan in Part 8. Translates strategy into month-by-month execution.
SKILL.md
yearly-planner.SKILL.mdname: yearly-planner
description: "Produce the 12-month operational Yearly Planner — the calendar companion to the Growth Plan in Part 8. Translates strategy into month-by-month execution."
user-invocable: true
triggers:
- produce the yearly planner
- generate 12-month operational calendar
- run part 8 yearly planner
- month-by-month execution plan
- quarterly themes and monthly initiatives
- operational calendar for the year
allowed-tools: Read Write Edit Bash Glob Grep
engagement-part: "8"
view-preference: v2-primary
/digital-marketing-pro:yearly-planner — Part 8 Operational Companion
The Yearly Planner complements the Growth Plan with a 12-month operational calendar that ties strategy to date-by-date execution. If the Growth Plan answers *"How will we grow this business?"*, the Yearly Planner answers *"What will we do, week by week, month by month?"*
**Specification:** [yearly-planner-template.md](../context-engine/yearly-planner-template.md) — the canonical structure.
Pre-conditions
The Yearly Planner is produced **after** the Growth Plan. It operationalises the Growth Plan's strategic decisions.
Before producing, verify:
1. **Growth Plan completed** at `part-08-growth-plan/growth-plan.md` 2. **Part 7 preparation documents available** (campaign architecture, content pillars, KPI tree) 3. **Living Project Instruction File current** 4. **Brand profile** specifies geographic operations (so seasonal context can be applied)
Structure (8 sections)
| # | Section | Source | |---|---------|--------| | 1 | Annual Themes | Synthesis of Growth Plan strategy across 4 quarters | | 2 | Monthly Calendar | 12 monthly sub-sections; Growth Plan Section 8 expanded | | 3 | Seasonal Strategy | Industry + cultural / festival seasonality (regional context) | | 4 | Campaign Architecture | Part 7 campaign architecture detailed by quarter | | 5 | Content Pillars Calendar | Core Doc 3.3 messaging pillars × Part 7 content pillars | | 6 | Channel-Specific Cadence | One sub-section per active channel family | | 7 | Resource & Budget Pacing | Quarterly budget pacing + resource plan | | 8 | Quarterly Review Schedule | QBR dates + decision authority per [reporting-cadence.md](../context-engine/reporting-cadence.md) |
Production process
Step 1: Read sources
- Growth Plan (canonical version)
- Living Project Instruction File
- Part 7 preparation documents
- Brand profile (for geography → seasonality)
- For India-operating brands: [india-market-context.md](../context-engine/india-market-context.md)
Step 2: Build the Annual Themes
Identify 4 quarterly themes that organise the year. Each theme is one sentence with strategic rationale and ladders into the overall positioning. Themes might be (this is one example pattern, customise per engagement):
- Q1: Foundation + initial demand capture
- Q2: Demand generation activation
- Q3: Account expansion + community
- Q4: Festive surge + awards / press push
Step 3: Detail the Monthly Calendar
12 sub-sections, ~1 page each. For each month:
- **Theme** — one sentence summary
- **Major initiatives** — 2-4 specific initiatives with owner and deadline
- **Always-on activity** — what continues from the prior month (paid ads at fixed budget, organic posting cadence, email programme, SEO content production)
- **Key dates** — product launches, industry events, holidays / festivals relevant to the brand, planned PR moments
- **Content calendar overview** — themes per week, content pillars covered, target volume per channel
- **Budget** — monthly fixed spend by channel, variable budget reserve
- **KPI targets** — primary + 2-3 secondary KPIs for the month
Step 4: Map Seasonal Strategy
For India-operating brands, reference the seasonality table from [india-market-context.md](../context-engine/india-market-context.md):
- Dussehra → Diwali (Sept-Nov) festive peak
- Wedding season (Nov-Feb)
- End of financial year (Jan-Mar) — B2B budget spend
- Back-to-school (Apr-Jun)
- Monsoon (Jun-Sep)
- Cricket / IPL season (Mar-May)
For other markets, apply equivalent seasonality. For B2B globally, fiscal year-end and major industry events are universal seasonality drivers.
Step 5: Map Campaign Architecture
The Part 7 campaign architecture document defines the year's major campaigns. The Yearly Planner places each campaign in its calendar slot with:
- Campaign name + theme
- Target persona
- Primary channels
- Timing (start, peak, wind-down)
- KPIs
- Expected outcome
Step 6: Map Content Pillars Calendar
The 3-5 content pillars from Core Doc 3.3 are scheduled across the year:
- Per-pillar production target for the year (volume per format)
- Quarterly distribution (how content mix shifts)
- Repurposing flow (long-form blog → social posts → video → email)
Step 7: Map Channel-Specific Cadence
For each active channel family:
- Posting / sending / publishing cadence (e.g., LinkedIn: 4 posts/week; Email: 1 broadcast/week + lifecycle flows; SEO: 6 articles/month)
- Volume targets for the year
- Quarterly emphasis shifts
- Resource requirements (creative production, copywriting, design, video)
Step 8: Produce companion files
The Yearly Planner is delivered as:
- **`yearly-planner.md`** (canonical)
- **`yearly-planner.pdf`** (client distribution via `pdf-generator.py`)
- **`yearly-planner.xlsx`** (calendar in spreadsheet form for ongoing operational use)
Save all to `engagements/{id}/part-08-growth-plan/`.
Quality discipline
1. **Every initiative has an owner.** "Marketing team will do X" is not actionable. 2. **Every quarter has measurable KPI targets.** "Improve traffic" is not a target. 3. **Always-on activity distinguished from initiatives.** Always-on is the baseline; initiatives are time-bounded efforts on top. 4. **Realistic capacity respected.** Sequence prevents burnout. 5. **Living document.** Reviewed and adjusted at each Quarterly Business Review. 6. **Aligns with Growth Plan.** No contradictions between
Read more
name: yearly-planner description: "Produce the 12-month operational Yearly Planner — the calendar companion to the Growth Plan in Part 8. Translates strategy into month-by-month execution." user-invocable: true triggers: - produce the yearly planner - generate 12-month operational calendar - run part 8 yearly planner - month-by-month execution plan - quarterly themes and monthly initiatives - operational calendar for the year allowed-tools: Read Write Edit Bash Glob Grep engagement-part: "8" view-preference: v2-primary
/digital-marketing-pro:yearly-planner — Part 8 Operational Companion
The Yearly Planner complements the Growth Plan with a 12-month operational calendar that ties strategy to date-by-date execution. If the Growth Plan answers *"How will we grow this business?"*, the Yearly Planner answers *"What will we do, week by week, month by month?"*
**Specification:** [yearly-planner-template.md](../context-engine/yearly-planner-template.md) — the canonical structure.
Pre-conditions
The Yearly Planner is produced **after** the Growth Plan. It operationalises the Growth Plan's strategic decisions.
Before producing, verify:
1. **Growth Plan completed** at `part-08-growth-plan/growth-plan.md` 2. **Part 7 preparation documents available** (campaign architecture, content pillars, KPI tree) 3. **Living Project Instruction File current** 4. **Brand profile** specifies geographic operations (so seasonal context can be applied)
Structure (8 sections)
| # | Section | Source | |---|---------|--------| | 1 | Annual Themes | Synthesis of Growth Plan strategy across 4 quarters | | 2 | Monthly Calendar | 12 monthly sub-sections; Growth Plan Section 8 expanded | | 3 | Seasonal Strategy | Industry + cultural / festival seasonality (regional context) | | 4 | Campaign Architecture | Part 7 campaign architecture detailed by quarter | | 5 | Content Pillars Calendar | Core Doc 3.3 messaging pillars × Part 7 content pillars | | 6 | Channel-Specific Cadence | One sub-section per active channel family | | 7 | Resource & Budget Pacing | Quarterly budget pacing + resource plan | | 8 | Quarterly Review Schedule | QBR dates + decision authority per [reporting-cadence.md](../context-engine/reporting-cadence.md) |
Production process
Step 1: Read sources
- Growth Plan (canonical version)
- Living Project Instruction File
- Part 7 preparation documents
- Brand profile (for geography → seasonality)
- For India-operating brands: [india-market-context.md](../context-engine/india-market-context.md)
Step 2: Build the Annual Themes
Identify 4 quarterly themes that organise the year. Each theme is one sentence with strategic rationale and ladders into the overall positioning. Themes might be (this is one example pattern, customise per engagement):
- Q1: Foundation + initial demand capture
- Q2: Demand generation activation
- Q3: Account expansion + community
- Q4: Festive surge + awards / press push
Step 3: Detail the Monthly Calendar
12 sub-sections, ~1 page each. For each month:
- **Theme** — one sentence summary
- **Major initiatives** — 2-4 specific initiatives with owner and deadline
- **Always-on activity** — what continues from the prior month (paid ads at fixed budget, organic posting cadence, email programme, SEO content production)
- **Key dates** — product launches, industry events, holidays / festivals relevant to the brand, planned PR moments
- **Content calendar overview** — themes per week, content pillars covered, target volume per channel
- **Budget** — monthly fixed spend by channel, variable budget reserve
- **KPI targets** — primary + 2-3 secondary KPIs for the month
Step 4: Map Seasonal Strategy
For India-operating brands, reference the seasonality table from [india-market-context.md](../context-engine/india-market-context.md):
- Dussehra → Diwali (Sept-Nov) festive peak
- Wedding season (Nov-Feb)
- End of financial year (Jan-Mar) — B2B budget spend
- Back-to-school (Apr-Jun)
- Monsoon (Jun-Sep)
- Cricket / IPL season (Mar-May)
For other markets, apply equivalent seasonality. For B2B globally, fiscal year-end and major industry events are universal seasonality drivers.
Step 5: Map Campaign Architecture
The Part 7 campaign architecture document defines the year's major campaigns. The Yearly Planner places each campaign in its calendar slot with:
- Campaign name + theme
- Target persona
- Primary channels
- Timing (start, peak, wind-down)
- KPIs
- Expected outcome
Step 6: Map Content Pillars Calendar
The 3-5 content pillars from Core Doc 3.3 are scheduled across the year:
- Per-pillar production target for the year (volume per format)
- Quarterly distribution (how content mix shifts)
- Repurposing flow (long-form blog → social posts → video → email)
Step 7: Map Channel-Specific Cadence
For each active channel family:
- Posting / sending / publishing cadence (e.g., LinkedIn: 4 posts/week; Email: 1 broadcast/week + lifecycle flows; SEO: 6 articles/month)
- Volume targets for the year
- Quarterly emphasis shifts
- Resource requirements (creative production, copywriting, design, video)
Step 8: Produce companion files
The Yearly Planner is delivered as:
- **`yearly-planner.md`** (canonical)
- **`yearly-planner.pdf`** (client distribution via `pdf-generator.py`)
- **`yearly-planner.xlsx`** (calendar in spreadsheet form for ongoing operational use)
Save all to `engagements/{id}/part-08-growth-plan/`.
Quality discipline
1. **Every initiative has an owner.** "Marketing team will do X" is not actionable. 2. **Every quarter has measurable KPI targets.** "Improve traffic" is not a target. 3. **Always-on activity distinguished from initiatives.** Always-on is the baseline; initiatives are time-bounded efforts on top. 4. **Realistic capacity respected.** Sequence prevents burnout. 5. **Living document.** Reviewed and adjusted at each Quarterly Business Review. 6. **Aligns with Growth Plan.** No contradictions between
Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?
Other skills on digital-marketing-pro.
- /ab-test-plan
Design A/B and multivariate tests. Use when: sample size calculation, testing hypothesis, CRO experimentation.
Open skill - /ad-creative
Generate platform-specific ad copy. Use when: Google RSA, Meta, LinkedIn, TikTok ad variations with quality scoring.
Open skill - /add-integration
Add MCP server integrations. Use when: connecting a custom tool, API, or service to the plugin via .mcp.json.
Open skill - /aeo-audit
Audit AI search visibility. Use when: checking brand presence in ChatGPT, Perplexity, AI Overviews, Gemini.
Open skill - /aeo-geo
Optimize AI engine visibility. Use when: AEO/GEO strategy, citation optimization, entity consistency across AI platforms.
Open skill - /agency-dashboard
Portfolio-level agency dashboard aggregating health metrics across all client brands — campaign status, budget pacing, KPI attainment, team utilization. Use when reviewing cross-brand portfolio health, preparing for agency leadership standups, or getting a single-view snapshot
Open skill

