communications-plan

communications-plan is a skill for Claude Code, Codex from fzfclee/consulting-skills. It costs 46 tokens per session (786 once invoked), scanned A, original, Apache-2.0.

A consulting method for planning communications around a decision, change, project, or stakeholder action. It defines who needs what message, from whom, through which channel, and when.

In plain words
What is it for?
Use it to coordinate announcements, change communication, stakeholder updates, and action plans. It helps clarify audiences, messages, channels, timing, and feedback paths.
Why use it?
It prevents communication plans from being vague or disconnected from the behavior people need to adopt. Missing information is recorded as an assumption with a follow-up check.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to coordinate announcements, change communication, stakeholder updates, and action plans. It helps clarify audiences, messages, channels, timing, and feedback paths.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fzfclee/consulting-skills/communications-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fzfclee/consulting-skills --skill communications-plan
Clone the repo
git clone --depth 1 https://github.com/fzfclee/consulting-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for communications-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/fzfclee/consulting-skills/communications-plan/github.svg)](https://agentmods.dev/skills/fzfclee/consulting-skills/communications-plan)
Your own site
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/communications-plan"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/communications-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for communications-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/communications-plan"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/communications-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 786 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00786
Opus 5 $0.00023 $0.00393
Sonnet 5 $0.00009 $0.00157
Haiku 4.5 $0.00005 $0.00079

Measured 10d ago against content hash 5a458008db73, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

communications-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/communications-plan/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Communications Plan

Use this skill to run Communications Plan as a practical consulting method, not as a generic framework explanation.

Method Notes

  • Segment by audience role and concern, not by org chart only.
  • Every message must specify sender, channel, timing, and requested action.

Required Inputs

Collect or infer these inputs before execution:

  • communication objective
  • audiences
  • messages
  • channels
  • timing constraints

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use before the audience, required behavior, sender, channel, timing, and feedback path are clear. Communication cannot compensate for missing authority, broken process, or misaligned incentives.

Adjacent Methods

  • change-impact-analysis: identify who is affected and what adoption support is needed.
  • raci-matrix: clarify who owns each communication decision and action.

Step-by-Step Execution

Step Required input How to execute Output
Set communication objective Decision/change, desired audience behavior, timing. Define what each audience must know, feel, decide, or do. Communication objective.
Segment audiences Stakeholders, power map, impact analysis, relationship facts. Group audiences by role, concern, impact, and required action. Audience segments.
Build message matrix Audience segments, evidence, likely objections. Write message, proof, tone, sender, channel, and timing for each segment. Audience-message matrix.
Set cadence and feedback Channels, decision timeline, meeting rhythm. Define update cadence, feedback collection, and escalation route. Cadence and feedback plan.
Check readiness Draft plan, risks, missing approvals. Identify message gaps, sensitive audiences, and first communication action. Ready-to-send communication plan.

Output Template

### 1. Communication Objective
Decision / behavior needed:
Audience scope:
Constraints:
Known concerns:

### 2. Audience Message Matrix
| Audience | Needed action | Message | Evidence / proof | Channel | Sender |
|---|---|---|---|---|---|
|  |  |  |  |  |  |

### 3. Cadence And Feedback
| Touchpoint | Timing | Owner | Feedback signal | Response rule |
|---|---|---|---|---|
|  |  |  |  |  |

### 4. Readiness Check
| Risk | Prevention | Trigger | Escalation |
|---|---|---|---|
|  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 87 lines · 46 tokens per session scan A 5a458008db73

Subscribe to this mod's changes

communications-plan is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 22d ago), licensed Apache-2.0. It adds 46 tokens to every session and 786 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.