Annual planning

Skill lpalokan/bmad-marketing-growth/skills/annual-planning

Annual marketing plan workflow. Lead: Max Growth (CMO Orchestrator). Produces a domain-by-domain plan, quarterly sequencing, budget split, and the brief packs each domain needs to start the year. Use when user says annual plan, year planning, or kickoff-of-year workflow.From its SKILL.md

Install

npx -y skills add lpalokan/bmad-marketing-growth --skill annual-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, as published. Nobody here has run it

Annual Planning Workflow

Overview

The kickoff-of-year workflow. Max Growth runs the planning sessions with the user, then issues per-domain quarterly briefs so each domain orchestrator (PMM, Brand, Content, Digital, Growth, Field, PR, Channel) can start their Q1 work against a single source of truth.

Phases

Inputs — Refresh company-context (run bootstrap if missing).
Strategy — Pick the 2-3 dominant motions per quarter.
Resourcing — Budget split + headcount + dependency map.
Domain briefs — Issue annual brief packs to each domain.
Cadence — Set the quarterly re-plan ritual.

Source Fidelity

These rules override the persona.

Never invent numbers about the user's business or industry. Metrics, percentages, dollar amounts, audience sizes, conversion rates, benchmarks — all numbers must come from a source: the user's input, a WebSearch result cited inline, or a file the user shared. Anything else is fabrication.
Missing data → ask, don't fill. If a step needs a number the user hasn't provided, ask one focused question before proceeding. Do not insert a plausible default.
Label examples. Sample emails / posts / dashboards / sequences that contain numbers must be prefixed Example — illustrative, not benchmarks.
Persona is style, not authority. Identity backstory ("Built X for Y companies", "Former Head of Z") is for tone — not a license to invent client names, study results, proprietary stats, or "I've seen this in 30+ companies"–style claims.

On Activation

Load configuration (tolerant of missing files; for each value, the first file that provides it wins):
- Try {project-root}/_bmad/custom/config.user.toml, then {project-root}/_bmad/custom/config.toml (pinned overrides -- always win when present).
- Try {project-root}/_bmad/marketing-growth/config.yaml (BMAD 6.x module config; flat keys user_name, communication_language, document_output_language, output_folder).
- Try {project-root}/_bmad/config.user.toml, then {project-root}/_bmad/config.toml (BMAD 6.x root config; [core] keys, e.g. output_folder, document_output_language).
- Legacy fallback: try {project-root}/_bmad/config.yaml (core.user_name, core.communication_language, core.document_output_language, marketing-growth.output_folder), with {project-root}/_bmad/config.user.yaml overriding core.user_name and core.communication_language.
- For any value still missing, use defaults: user_name = there, communication_language = English, document_output_language = English.
- Resolve output_folder silently — never ask the user. Normalize a relative value against {project-root}. Then use the first of these that already contains a company-context/ folder: the configured value, {project-root}/output, {project-root}/_bmad-output (legacy name, retired in v2.4). If none does, glob the project for **/company-context/index.md and **/company-context/icp.md (excluding .git/, node_modules/, _bmad/, **/work/**) and use its parent when there is exactly one match. Still nothing: use {project-root}/output. output/ is the canonical name; _bmad-output/ is read-only compatibility — never create it.
Confirm company-context exists: {output_folder}/company-context/icp.md, positioning.md, kpis.md. Read whichever are present and note what is absent. Only if none exists anywhere in the project, suggest /company-context-bootstrap and ask whether to continue without it.
Load and execute the sibling workflow.yaml phase by phase. Delegate to specialist agents as directed.
Save outputs to {output_folder}/work/{yyyy}-annual-plan/.