메뉴
This skill should be used when the user asks for a "change comms plan," "communications calendar for this transformation," "what do we tell each audience and when," or needs audience × message × channel × timing before go-live.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | communications-plan |
| description | This skill should be used when the user asks for a "change comms plan," "communications calendar for this transformation," "what do we tell each audience and when," or needs audience × message × channel × timing before go-live. |
| allowed-tools | Read, Grep, Glob |
| metadata | {"version":"0.3.0","owner":"change-management practice","review_cadence":"quarterly","work_shape":"structured-aggregation","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"} |
Build a structured comms plan from stakeholder segments and program milestones — completeness and sequencing, not polished copy.
/change-management:stakeholder-impact-map if audiences undefined.| Input | If missing |
|---|---|
| Stakeholder segments or audience list | Ask or infer from scope; flag gaps |
| Key milestones (go-live, pilot, training) | Ask timeline |
| Practice profile comms approval path | Note default approval; [PROVISIONAL] |
Without milestones: sequence by relative phase only (T-minus labels); flag dates as [TBD].
Structured-aggregation bands; every row has owner and approval note; no fabricated quotes from leadership.
Read practice profile — comms ownership, approval path, channel preferences.
Use stakeholder impact map if available — audiences = segments plus any additional governance audiences (steering, unions, regulators).
For each milestone window, define comms rows:
Sequencing checks:
Gap check — high-impact segments with no comms row before go-live; duplicate messages to same audience same week.
MILESTONES: [list with dates or T-labels]
APPROVAL PATH: [from profile or PROVISIONAL default]
| Timing | Audience | Message intent | Channel | Sender | Owner | Approval |
|---|---|---|---|---|---|---|
| ... | ... | ... | ... | ... | ... | ... |
SEQUENCING FLAGS: [violations, or "none"]
AUDIENCE GAPS: [high-impact segments with no row, or "none"]
DUPLICATE / NOISE FLAGS: [same audience overloaded, or "none"]
Input: CRM go-live Friday; no prior manager briefing row.
Expected output: SEQUENCING FLAGS — manager cascade missing before frontline announcement; add T-7 manager prep row.
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/change-management/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /change-management:practice-setup auto-applies a full profile write.
Follows plugin CLAUDE.md § Outputs. Next: draft copy in session or /consulting:exec-memo for sponsor summary when installed.
Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.
Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.
Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.
Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.
This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.
This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.