agentleFS
fzfcleefzfclee/consulting-skills/skills/communications-plan/SKILL.md

communications-plan

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Use when a decision, change, project, or stakeholder move needs coordinated communication. Use when applying the Communications Plan consulting method and when a user asks for Communications Plan, method execution, structured diagnosis, or action planning.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 9
  2. Distinctive:

    Every message must specify sender, channel, timing, and requested action.

    line 14
  3. Very specific:

    If an input is missing, do not block automatically.

    line 26
  4. Distinctive:

    Keep wording professional and plain enough that a smart non-specialist can use the output directly.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

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

Use a marked planning draft to clarify missing audience, required behavior, sender, channel, timing, approval, or feedback ownership. Do not describe a plan as ready until applicable prerequisites are confirmed; a confirmed unmet prerequisite blocks readiness. Communication cannot compensate for missing authority, broken process, or misaligned incentives. Readiness is a planning assessment and does not grant permission to send.

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

StepRequired inputHow to executeOutput
Set communication objectiveDecision/change, desired audience behavior, timing.Define what each audience must know, feel, decide, or do.Communication objective.
Segment audiencesStakeholders, power map, impact analysis, relationship facts.Group audiences by role, concern, impact, and required action.Audience segments.
Build message matrixAudience segments, evidence, likely objections.Write message, proof, tone, sender, channel, and timing for each segment.Audience-message matrix.
Set cadence and feedbackChannels, decision timeline, meeting rhythm.Define update cadence, feedback collection, and escalation route.Cadence and feedback plan.
Check readinessDraft plan, risks, applicable approvals and feedback ownership.Report draft / blocked / ready: draft while information or confirmation is missing, blocked when a known prerequisite is unmet, ready only when applicable prerequisites are confirmed. List gaps and next actions.Communication plan and readiness status.

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
Status: draft / blocked / ready
Applicable prerequisites, confirmation evidence, and gaps:
| Risk | Prevention | Trigger | Escalation |
|---|---|---|---|
|  |  |  |  |

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

Quality Gate

  • Produce the method-specific outputs for Communication Objective, Audience Message Matrix, Cadence And Feedback; do not substitute a generic framework summary.
  • Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
  • Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
  • Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
  • State missing inputs and the smallest validation action instead of inventing precision.
  • Missing approval or feedback ownership permits a labeled draft, not a ready claim; retain the readiness status, evidence and next clarification action. This artifact does not grant permission to send.
  • Keep wording professional and plain enough that a smart non-specialist can use the output directly.

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.