SkillAgentSearch skills...

yearly-planner

Produce the 12-month operational Yearly Planner — the Part 8 calendar companion to the Growth Plan — with quarterly themes, 12 monthly sections (initiatives with owners, key dates, budget, KPI targets), seasonal strategy, campaign and content-pillar calendars, and channel cadence, delivered as markd…

Install / Use

npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of yearly-planner

yearly-planner scores 87/100 on our quality scale, 602nd of 1,213 Content & Media skills we index (top 50%).

Its SKILL.md is 8.2 KB long, well organised into 18 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

It has 832 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 26 days ago, so yearly-planner is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

yearly-planner compared with similar skills

All 4 of these similar skills score higher than yearly-planner; compare them before choosing.

SkillScoreStarsUpdatedFormat
yearly-planner (this skill)by indranilbanerjee8783226d agoSKILL.md
Agent-Reachby Panniantong10090.1k18d agoCLAUDE.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k11d agoSKILL.md
pptxby anthropics100177.9k11d agoSKILL.md

Frequently asked questions

How do I install yearly-planner?
Run npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner. The install tabs above show the steps for each supported agent.
Which AI agents does yearly-planner work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is yearly-planner safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is yearly-planner still maintained?
The repository was last updated 26 days ago, so yearly-planner is actively maintained.

name: yearly-planner description: "Produce the 12-month operational Yearly Planner — the Part 8 calendar companion to the Growth Plan — with quarterly themes, 12 monthly sections (initiatives with owners, key dates, budget, KPI targets), seasonal strategy, campaign and content-pillar calendars, and channel cadence, delivered as markdown, PDF, and XLSX. Triggers on "/digital-marketing-pro:yearly-planner", "produce the yearly planner", "month-by-month execution plan", "operational calendar for the year", "quarterly themes and monthly initiatives". Requires a completed Growth Plan and Part 7 preparation docs; reads the brand profile for geography-driven seasonality and marks Part 8 complete in the engagement workflow." user-invocable: true 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 — 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 |

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

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:

  • 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 the two.

After production

  1. Save all formats to part-08-growth-plan/
  2. Mark Part 8 fully completed via engagement-state.py mark-part-completed --part 8
  3. Update LIF: Engagement phase = "Strategy approved; Channel Build (Part 9) ready to begin"
  4. Brief: "Yearly Planner complete. Operational calendar covers 12 months with quarterly themes, monthly initiatives, and channel-specific cadence. Recommend reviewing with the client before kicking off Part 9 channel build. /digital-marketing-pro:engagement next to advance."

Examples

Example 1: Standard Yearly Planner production

User: Produce the Yearly Planner for Acme.

Skill response:
1. Verify Growth Plan exists ✓; Part 7 preparation docs available ✓
2. Read Growth Plan, Part 7 docs, brand profile (geography: India)
3. Apply India seasonality: Q3 includes Dussehra-Diwali surge planning; Q4 includes wedding season prep
4. Build 4 quarterly themes
5. Detail 12 monthly sections with initiatives, dates, budget, KPIs
6. Schedule 6 major campaigns across the year (Q1: launch; Q2: growth-acceleration; Q3: festive; Q4: awards-PR push)
7. Map content pillars: Pillar A 40%, B 25%, C 20%, D 15% of annual production
8. Generate markdown + PDF + XLSX
9. Mark Part 8 complete
10. Brief: "Yearly Planner complete. 12 months, 6 major campaigns, 48 content pieces planned, 4 quarterly review checkpoints. Festive season Q3 has 2x normal budget pacing per Diwali surge. /digital-marketing-pro:engagement next moves to Part 9."

Related skills

  • growth-plan — companion deliverable; produced first
  • engagement-workflow — orchestrates Part 8

Related references

Related Skills

View on GitHub
GitHub Stars832
CategoryContent
Updated26d ago
Forks136

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions