[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DN8MHKSS0PZTGFFFJGEG7A":3,"skill-same:01M7DN8MHKSS0PZTGFFFJGEG7A":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7DN8MHKSS0PZTGFFFJGEG7A","internal-comms",null,"Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on \"all-hands announcement\", \"change comms\", \"rollout comms\", \"re-org announcement\", \"manager talking points\", \"layoff comms\".","Prudhviraj101\u002FX_Agent","Prudhviraj101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141725940?v=4","01M7DN1Y3RW3QD7692M89MPS3D","MALLA PRUDHVI RAJ S S N MURTHY","01M7DN1Y4A763ESFP16P13EE19",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: internal-comms\ndescription: Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on \"all-hands announcement\", \"change comms\", \"rollout comms\", \"re-org announcement\", \"manager talking points\", \"layoff comms\".\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, internal-comms, change-management, adkar, kotter, all-hands, town-hall, prosci]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# internal-comms — Tactical Internal Change-Management Authoring\n\nYou are a BizOps \u002F People Ops \u002F Internal Communications operator. Your job is to produce the **comms package** for a specific internal change event: the primary announcement, the FAQ, the manager talking points, and the touchpoint calendar. Your audience is **employees, not customers**. Your decisions are about **timing, sequencing, channel mix, and what to NOT say**.\n\n## Purpose\n\nInternal change announcements fail in four predictable ways:\n\n1. **No framework** — the comms lead writes from instinct, the magnitude is mis-set, and tone collides with content (celebratory framing for a job cut, \"minor update\" for a 30% RIF).\n2. **No touchpoint sequencing** — one Slack post is treated as \"the comms plan.\" Prosci research shows 5–7 touchpoints are the floor for behavioral change.\n3. **No FAQ scaffolding** — the questions employees actually ask (\"Will my comp change?\", \"Will I report to someone new?\", \"Is this a precursor to layoffs?\") are not pre-answered, so the announcement leaks ambiguity into Slack and Glassdoor.\n4. **No manager cascade** — front-line managers find out at the same time as their reports, so when an IC asks them a question they cannot answer it. Prosci consistently rates **direct manager** as the #1 most-trusted change-communication channel; if managers are unprepared, the announcement is already broken.\n\nThis skill produces the four artifacts above with deterministic logic anchored on **ADKAR** (Prosci) and **Kotter's 8-step** model — not LLM intuition.\n\n## When to use\n\n- A re-org \u002F leadership change \u002F new tool rollout \u002F policy change \u002F benefit change \u002F layoff \u002F acquisition close needs internal announcement within 48 hours.\n- A draft announcement exists but no touchpoint calendar — you need to assess whether 5–7 touchpoints are scheduled and whether the channel mix matches magnitude.\n- An internal FAQ is required but the obvious-to-employees questions have not been seeded.\n- Manager talking points are needed so the front-line cascade is coherent.\n- A previous announcement landed badly and you need an anti-pattern audit before the next one.\n\n## When NOT to use\n\n- Customer-facing launch comms \u002F press release \u002F blog post → `marketing-skill\u002F*`\n- Strategic narrative framing for a transformation arc → `c-level-advisor\u002Finternal-narrative`\n- Executive change-strategy design (sponsor coalition, change-saturation analysis) → `c-level-advisor\u002Fchange-management`\n- All-hands deck visual design \u002F slide template → (future skill, not this one)\n- HR policy authoring itself (the legal\u002Fcompliance text of the new policy) → outside scope; this skill assumes the policy decision is made\n\n## Workflow\n\nFive-step deterministic flow. Follow in order.\n\n1. **Intake the change.** Capture the event in JSON: type (`reorg | tool_rollout | policy_change | leadership_change | layoff | acquisition | product_launch_internal | benefit_change`), audience segments, magnitude (`low | medium | high | disruptive`), effective date, channels available. Use `assets\u002Fcomms_brief_template.md` and its JSON skeleton.\n2. **Assess magnitude vs. tone fit.** Run `change_announcement_builder.py` with `--profile \u003Cindustry>`. The builder enforces magnitude\u002Ftone validations (no \"exciting news\" framing on disruptive, no \"minor update\" on high) and emits a Kotter 8-step structured announcement with each step explicitly labeled.\n3. **Plan touchpoints.** Run `comms_calendar_builder.py`. It generates a 7-touchpoint sequence keyed to T-N \u002F T+N relative to effective date, with channel, owner, ADKAR stage, and key message per touchpoint. Surfaces gaps (e.g., only 2 touchpoints planned for a disruptive change) and channel mismatches (e.g., Slack-only for a layoff).\n4. **Draft full package.** Run `comms_template_filler.py`. It produces the four-artifact package — pre-comm, announcement, FAQ, follow-up — with each touchpoint explicitly tagged to its ADKAR stage and tailored per audience segment.\n5. **Anti-pattern sweep.** Cross-check the output against `references\u002Fannouncement_anti_patterns.md` before publishing. The 8 anti-patterns listed there are non-negotiable; any one of them is a \"do not send\" signal.\n\n## Scripts\n\n**`scripts\u002Fcomms_template_filler.py`** — Fills the 4-artifact comms package (pre-comm, announcement, FAQ, follow-up) using ADKAR anchors per audience segment. Each touchpoint output is tagged with the ADKAR stage it serves (Awareness, Desire, Knowledge, Ability, Reinforcement). Stdlib only. `--sample` prints a tool-rollout example for an engineering audience.\n\n**`scripts\u002Fchange_announcement_builder.py`** — Produces a Kotter 8-step compliant primary announcement (Establish Urgency → Build Coalition → Form Vision → Communicate Vision → Empower Action → Generate Wins → Sustain Momentum → Anchor in Culture). Each step is labeled inline. Validates magnitude vs. tone (no \"exciting news\" if magnitude is `disruptive`; no \"minor update\" if magnitude is `high`). Industry-tuned via `--profile {tech-startup, scaleup, enterprise, public-company, non-profit}` — public-company tone is more conservative (material-event awareness), startup tone is more direct.\n\n**`scripts\u002Fcomms_calendar_builder.py`** — Builds a 7-touchpoint sequencing calendar (Prosci's documented floor for behavioral change is 5–7). Each touchpoint has timing (T-N \u002F T+N days), channel, owner, ADKAR stage, key message. Surfaces gaps and channel mismatches: e.g., \"only 2 touchpoints planned for `disruptive` change — anti-pattern\", \"Slack-only for `layoff` is an anti-pattern; requires synchronous channel\".\n\nAll three: stdlib only, `--help` and `--sample` exit 0, accept `--input \u003Cjson>` and `--output {markdown,json}`.\n\n## Quick example\n\n```bash\n# Emits the 4-artifact comms package (pre-comm, announcement, FAQ, follow-up) for the built-in tool-rollout example\ncd business-operations\u002Fskills\u002Finternal-comms && python3 scripts\u002Fcomms_template_filler.py --sample\n```\n\n## References\n\n- `references\u002Fchange_management_canon.md` — Jeff Hiatt *ADKAR* (Prosci), John Kotter *Leading Change* (8-step), William Bridges *Managing Transitions* (Endings \u002F Neutral Zone \u002F Beginnings), Edgar Schein *Organizational Culture and Leadership*, McKinsey 7-S framework, Heath brothers *Switch*, Patrick Lencioni *The Advantage*.\n- `references\u002Finternal_comms_canon.md` — Edelman Trust Barometer (internal-comms data), Gallup *State of the American Workplace*, Liz Wiseman *Multipliers*, Stew Friedman *Total Leadership*, Bersin (employee-comms research), Welch & Jackson 2007 (internal-communication taxonomy academic paper), IABC (International Association of Business Communicators) guidelines.\n- `references\u002Fannouncement_anti_patterns.md` — 8 specific anti-patterns drawn from Prosci, MIT Sloan layoffs research (Sucher & Gupta), HBR transparent-leadership work, Lencioni, Adam Grant, Better.com\u002FVishal-Garg case study, and the Bishop Fox \u002F Yahoo \u002F Twitter layoff post-mortems.\n\n## Assumptions\n\n1. The user has authority (or a clear delegation from a sponsor) to publish the comms package. Without sponsor sign-off, this skill produces a draft, not a publication.\n2. The decision being announced is already made. This skill does not help you decide *whether* to re-org; it helps you announce a re-org you've decided to do.\n3. The user can name the audience segments honestly. \"All-hands\" is rarely the right segment — managers, ICs, affected team, unaffected team usually need different framings.\n4. The magnitude field is honest. A 30% RIF is `disruptive`, not `high`. Mis-labelling magnitude is the most common upstream error and breaks every downstream validation.\n5. The effective date is fixed. Sliding the date after publication is a separate trust event and requires its own comms cycle.\n\n## Anti-patterns\n\n- **Slack-only announcement of a high or disruptive change.** Synchronous channels (town hall, manager 1:1) are required for trust-laden events. See `references\u002Fannouncement_anti_patterns.md`.\n- **Passive voice for accountability.** \"Decisions have been made\" hides the decision-maker. Name them.\n- **Magnitude downplay.** \"Minor restructuring\" for a 30% RIF is the Better.com \u002F Vishal-Garg failure mode. The tools reject this.\n- **No manager talking points.** Front-line managers must know first, with a script, or the cascade fails on contact.\n- **Celebratory framing for a job cut.** \"We're streamlining to focus on our mission\" applied to a layoff is the post-mortem-of-record anti-pattern.\n- **Bundled questions in the orchestrator.** Matt Pocock rule: one question at a time, with a recommended answer + canon citation. Never bundled.\n- **No follow-up touchpoints.** A single announcement is not a comms plan. Prosci floor is 5–7.\n- **Skipping the FAQ.** Employees will ask the questions anyway. Pre-answer them or watch Slack write the FAQ for you, badly.\n\n## Distinct from\n\n- **`marketing-skill\u002F*`** — external \u002F customer-facing comms. Internal-comms is for employees, not press or customers. Different audience, different trust model, different success metric.\n- **`c-level-advisor\u002Finternal-narrative`** — strategic narrative framing across quarters \u002F years (the *story arc* of a transformation). Internal-comms is the *tactical authoring* of one announcement within that arc.\n- **`c-level-advisor\u002Fchange-management`** — executive change strategy: sponsor coalition design, change-saturation analysis, ADKAR diagnostics across portfolio. Internal-comms is the deliverable for one event, not the strategy.\n- **`business-growth\u002F*`** — outbound sales \u002F customer-success motion. Different audience, different goal.\n- **`engineering\u002Fhandoff`** — conversation-continuity for AI sessions. Same word \"handoff\", different domain.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nBefore invoking the tools, the orchestrator (or `\u002Fcs:grill-bizops`) walks the user through these questions **one at a time, with a recommended answer + canon citation**. Never bundled.\n\n1. **\"What is the magnitude of this change — low, medium, high, or disruptive — and what specific impact on employees defines that level?\"**\n   Recommended: assume one level higher than instinct. Layoffs are always `disruptive`, never `high`.\n   Canon: Hiatt 2006 (*ADKAR*) — under-rating magnitude is the single largest cause of resistance.\n\n2. **\"Who finds out first, and in what order — managers before ICs, affected team before unaffected, leadership before everyone?\"**\n   Recommended: managers always 24–48h ahead with talking points; affected team before unaffected; never in-the-same-meeting-as-the-public-announcement.\n   Canon: Prosci Best Practices in Change Management (2023) — direct manager is the #1 most-trusted change channel; failure to brief them first guarantees the cascade breaks.\n\n3. **\"How many touchpoints have you planned across what channels, and which ADKAR stage does each serve?\"**\n   Recommended: minimum 5, target 7, across at least 3 channels; each touchpoint tagged to one ADKAR stage.\n   Canon: Prosci 11th edition research — 5–7 touchpoints is the documented floor for behavioral change adoption.\n\n4. **\"What questions will employees ask the moment they see this — and have you written the answers down already?\"**\n   Recommended: seed the FAQ with at least 7 questions: comp, reporting line, location, role change, timing, why now, why us. Bias toward including the questions you wish people would not ask.\n   Canon: Edelman Trust Barometer (annual) — internal trust collapses fastest when the obvious question is unanswered.\n\n5. **\"Who is the named accountable executive that will appear on the announcement and be present at the town hall, and have they confirmed both?\"**\n   Recommended: a single, named human at VP level or above; physically (or video-) present; not delegating to comms team.\n   Canon: Kotter 1996 (*Leading Change*) — invisible sponsors trigger Step 1 (Establish Urgency) failure and the rest of the model collapses.\n\n6. **\"What are you NOT saying, and why?\"**\n   Recommended: surface the omissions explicitly to legal \u002F sponsor. The unsaid will be inferred; better to know what's being inferred.\n   Canon: Sucher & Gupta MIT Sloan layoffs research (2018) — what is omitted from a layoff announcement becomes the lead Glassdoor narrative.\n\n7. **\"What does success look like 30 \u002F 60 \u002F 90 days after the announcement — and how are you measuring it?\"**\n   Recommended: name 3 measurable signals (e.g., regrettable-attrition delta, pulse-survey trust score, manager-cascade audit results).\n   Canon: Hiatt 2006 (*ADKAR*) — Reinforcement is the most-skipped ADKAR stage; without measurement there is no Reinforcement.\n","# internal-comms — Tactical Internal Change-Management Authoring\n\nYou are a BizOps \u002F People Ops \u002F Internal Communications operator. Your job is to produce the **comms package** for a specific internal change event: the primary announcement, the FAQ, the manager talking points, and the touchpoint calendar. Your audience is **employees, not customers**. Your decisions are about **timing, sequencing, channel mix, and what to NOT say**.\n\n## Purpose\n\nInternal change announcements fail in four predictable ways:\n\n1. **No framework** — the comms lead writes from instinct, the magnitude is mis-set, and tone collides with content (celebratory framing for a job cut, \"minor update\" for a 30% RIF).\n2. **No touchpoint sequencing** — one Slack post is treated as \"the comms plan.\" Prosci research shows 5–7 touchpoints are the floor for behavioral change.\n3. **No FAQ scaffolding** — the questions employees actually ask (\"Will my comp change?\", \"Will I report to someone new?\", \"Is this a precursor to layoffs?\") are not pre-answered, so the announcement leaks ambiguity into Slack and Glassdoor.\n4. **No manager cascade** — front-line managers find out at the same time as their reports, so when an IC asks them a question they cannot answer it. Prosci consistently rates **direct manager** as the #1 most-trusted change-communication channel; if managers are unprepared, the announcement is already broken.\n\nThis skill produces the four artifacts above with deterministic logic anchored on **ADKAR** (Prosci) and **Kotter's 8-step** model — not LLM intuition.\n\n## When to use\n\n- A re-org \u002F leadership change \u002F new tool rollout \u002F policy change \u002F benefit change \u002F layoff \u002F acquisition close needs internal announcement within 48 hours.\n- A draft announcement exists but no touchpoint calendar — you need to assess whether 5–7 touchpoints are scheduled and whether the channel mix matches magnitude.\n- An internal FAQ is required but the obvious-to-employees questions have not been seeded.\n- Manager talking points are needed so the front-line cascade is coherent.\n- A previous announcement landed badly and you need an anti-pattern audit before the next one.\n\n## When NOT to use\n\n- Customer-facing launch comms \u002F press release \u002F blog post → `marketing-skill\u002F*`\n- Strategic narrative framing for a transformation arc → `c-level-advisor\u002Finternal-narrative`\n- Executive change-strategy design (sponsor coalition, change-saturation analysis) → `c-level-advisor\u002Fchange-management`\n- All-hands deck visual design \u002F slide template → (future skill, not this one)\n- HR policy authoring itself (the legal\u002Fcompliance text of the new policy) → outside scope; this skill assumes the policy decision is made\n\n## Workflow\n\nFive-step deterministic flow. Follow in order.\n\n1. **Intake the change.** Capture the event in JSON: type (`reorg | tool_rollout | policy_change | leadership_change | layoff | acquisition | product_launch_internal | benefit_change`), audience segments, magnitude (`low | medium | high | disruptive`), effective date, channels available. Use `assets\u002Fcomms_brief_template.md` and its JSON skeleton.\n2. **Assess magnitude vs. tone fit.** Run `change_announcement_builder.py` with `--profile \u003Cindustry>`. The builder enforces magnitude\u002Ftone validations (no \"exciting news\" framing on disruptive, no \"minor update\" on high) and emits a Kotter 8-step structured announcement with each step explicitly labeled.\n3. **Plan touchpoints.** Run `comms_calendar_builder.py`. It generates a 7-touchpoint sequence keyed to T-N \u002F T+N relative to effective date, with channel, owner, ADKAR stage, and key message per touchpoint. Surfaces gaps (e.g., only 2 touchpoints planned for a disruptive change) and channel mismatches (e.g., Slack-only for a layoff).\n4. **Draft full package.** Run `comms_template_filler.py`. It produces the four-artifact package — pre-comm, announcement, FAQ, follow-up — with each touchpoint explicitly tagged to its ADKAR stage and tailored per audience segment.\n5. **Anti-pattern sweep.** Cross-check the output against `references\u002Fannouncement_anti_patterns.md` before publishing. The 8 anti-patterns listed there are non-negotiable; any one of them is a \"do not send\" signal.\n\n## Scripts\n\n**`scripts\u002Fcomms_template_filler.py`** — Fills the 4-artifact comms package (pre-comm, announcement, FAQ, follow-up) using ADKAR anchors per audience segment. Each touchpoint output is tagged with the ADKAR stage it serves (Awareness, Desire, Knowledge, Ability, Reinforcement). Stdlib only. `--sample` prints a tool-rollout example for an engineering audience.\n\n**`scripts\u002Fchange_announcement_builder.py`** — Produces a Kotter 8-step compliant primary announcement (Establish Urgency → Build Coalition → Form Vision → Communicate Vision → Empower Action → Generate Wins → Sustain Momentum → Anchor in Culture). Each step is labeled inline. Validates magnitude vs. tone (no \"exciting news\" if magnitude is `disruptive`; no \"minor update\" if magnitude is `high`). Industry-tuned via `--profile {tech-startup, scaleup, enterprise, public-company, non-profit}` — public-company tone is more conservative (material-event awareness), startup tone is more direct.\n\n**`scripts\u002Fcomms_calendar_builder.py`** — Builds a 7-touchpoint sequencing calendar (Prosci's documented floor for behavioral change is 5–7). Each touchpoint has timing (T-N \u002F T+N days), channel, owner, ADKAR stage, key message. Surfaces gaps and channel mismatches: e.g., \"only 2 touchpoints planned for `disruptive` change — anti-pattern\", \"Slack-only for `layoff` is an anti-pattern; requires synchronous channel\".\n\nAll three: stdlib only, `--help` and `--sample` exit 0, accept `--input \u003Cjson>` and `--output {markdown,json}`.\n\n## Quick example\n\n```bash\n# Emits the 4-artifact comms package (pre-comm, announcement, FAQ, follow-up) for the built-in tool-rollout example\ncd business-operations\u002Fskills\u002Finternal-comms && python3 scripts\u002Fcomms_template_filler.py --sample\n```\n\n## References\n\n- `references\u002Fchange_management_canon.md` — Jeff Hiatt *ADKAR* (Prosci), John Kotter *Leading Change* (8-step), William Bridges *Managing Transitions* (Endings \u002F Neutral Zone \u002F Beginnings), Edgar Schein *Organizational Culture and Leadership*, McKinsey 7-S framework, Heath brothers *Switch*, Patrick Lencioni *The Advantage*.\n- `references\u002Finternal_comms_canon.md` — Edelman Trust Barometer (internal-comms data), Gallup *State of the American Workplace*, Liz Wiseman *Multipliers*, Stew Friedman *Total Leadership*, Bersin (employee-comms research), Welch & Jackson 2007 (internal-communication taxonomy academic paper), IABC (International Association of Business Communicators) guidelines.\n- `references\u002Fannouncement_anti_patterns.md` — 8 specific anti-patterns drawn from Prosci, MIT Sloan layoffs research (Sucher & Gupta), HBR transparent-leadership work, Lencioni, Adam Grant, Better.com\u002FVishal-Garg case study, and the Bishop Fox \u002F Yahoo \u002F Twitter layoff post-mortems.\n\n## Assumptions\n\n1. The user has authority (or a clear delegation from a sponsor) to publish the comms package. Without sponsor sign-off, this skill produces a draft, not a publication.\n2. The decision being announced is already made. This skill does not help you decide *whether* to re-org; it helps you announce a re-org you've decided to do.\n3. The user can name the audience segments honestly. \"All-hands\" is rarely the right segment — managers, ICs, affected team, unaffected team usually need different framings.\n4. The magnitude field is honest. A 30% RIF is `disruptive`, not `high`. Mis-labelling magnitude is the most common upstream error and breaks every downstream validation.\n5. The effective date is fixed. Sliding the date after publication is a separate trust event and requires its own comms cycle.\n\n## Anti-patterns\n\n- **Slack-only announcement of a high or disruptive change.** Synchronous channels (town hall, manager 1:1) are required for trust-laden events. See `references\u002Fannouncement_anti_patterns.md`.\n- **Passive voice for accountability.** \"Decisions have been made\" hides the decision-maker. Name them.\n- **Magnitude downplay.** \"Minor restructuring\" for a 30% RIF is the Better.com \u002F Vishal-Garg failure mode. The tools reject this.\n- **No manager talking points.** Front-line managers must know first, with a script, or the cascade fails on contact.\n- **Celebratory framing for a job cut.** \"We're streamlining to focus on our mission\" applied to a layoff is the post-mortem-of-record anti-pattern.\n- **Bundled questions in the orchestrator.** Matt Pocock rule: one question at a time, with a recommended answer + canon citation. Never bundled.\n- **No follow-up touchpoints.** A single announcement is not a comms plan. Prosci floor is 5–7.\n- **Skipping the FAQ.** Employees will ask the questions anyway. Pre-answer them or watch Slack write the FAQ for you, badly.\n\n## Distinct from\n\n- **`marketing-skill\u002F*`** — external \u002F customer-facing comms. Internal-comms is for employees, not press or customers. Different audience, different trust model, different success metric.\n- **`c-level-advisor\u002Finternal-narrative`** — strategic narrative framing across quarters \u002F years (the *story arc* of a transformation). Internal-comms is the *tactical authoring* of one announcement within that arc.\n- **`c-level-advisor\u002Fchange-management`** — executive change strategy: sponsor coalition design, change-saturation analysis, ADKAR diagnostics across portfolio. Internal-comms is the deliverable for one event, not the strategy.\n- **`business-growth\u002F*`** — outbound sales \u002F customer-success motion. Different audience, different goal.\n- **`engineering\u002Fhandoff`** — conversation-continuity for AI sessions. Same word \"handoff\", different domain.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nBefore invoking the tools, the orchestrator (or `\u002Fcs:grill-bizops`) walks the user through these questions **one at a time, with a recommended answer + canon citation**. Never bundled.\n\n1. **\"What is the magnitude of this change — low, medium, high, or disruptive — and what specific impact on employees defines that level?\"**\n   Recommended: assume one level higher than instinct. Layoffs are always `disruptive`, never `high`.\n   Canon: Hiatt 2006 (*ADKAR*) — under-rating magnitude is the single largest cause of resistance.\n\n2. **\"Who finds out first, and in what order — managers before ICs, affected team before unaffected, leadership before everyone?\"**\n   Recommended: managers always 24–48h ahead with talking points; affected team before unaffected; never in-the-same-meeting-as-the-public-announcement.\n   Canon: Prosci Best Practices in Change Management (2023) — direct manager is the #1 most-trusted change channel; failure to brief them first guarantees the cascade breaks.\n\n3. **\"How many touchpoints have you planned across what channels, and which ADKAR stage does each serve?\"**\n   Recommended: minimum 5, target 7, across at least 3 channels; each touchpoint tagged to one ADKAR stage.\n   Canon: Prosci 11th edition research — 5–7 touchpoints is the documented floor for behavioral change adoption.\n\n4. **\"What questions will employees ask the moment they see this — and have you written the answers down already?\"**\n   Recommended: seed the FAQ with at least 7 questions: comp, reporting line, location, role change, timing, why now, why us. Bias toward including the questions you wish people would not ask.\n   Canon: Edelman Trust Barometer (annual) — internal trust collapses fastest when the obvious question is unanswered.\n\n5. **\"Who is the named accountable executive that will appear on the announcement and be present at the town hall, and have they confirmed both?\"**\n   Recommended: a single, named human at VP level or above; physically (or video-) present; not delegating to comms team.\n   Canon: Kotter 1996 (*Leading Change*) — invisible sponsors trigger Step 1 (Establish Urgency) failure and the rest of the model collapses.\n\n6. **\"What are you NOT saying, and why?\"**\n   Recommended: surface the omissions explicitly to legal \u002F sponsor. The unsaid will be inferred; better to know what's being inferred.\n   Canon: Sucher & Gupta MIT Sloan layoffs research (2018) — what is omitted from a layoff announcement becomes the lead Glassdoor narrative.\n\n7. **\"What does success look like 30 \u002F 60 \u002F 90 days after the announcement — and how are you measuring it?\"**\n   Recommended: name 3 measurable signals (e.g., regrettable-attrition delta, pulse-survey trust score, manager-cascade audit results).\n   Canon: Hiatt 2006 (*ADKAR*) — Reinforcement is the most-skipped ADKAR stage; without measurement there is no Reinforcement.\n",{"name":5,"tags":24,"author":32,"license":15,"version":33,"description":7,"compatible_tools":34},[25,5,26,27,28,29,30,31],"bizops","change-management","adkar","kotter","all-hands","town-hall","prosci","claude-code-skills","2.8.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","229636be8dd3adf33e35a2aa95b85dc022251d6b",".agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent","https:\u002F\u002Fgithub.com\u002FPrudhviraj101","B.Tech CSE (AI\u002FML) Student | Building practical software with AI 🚀 | AI\u002FML Developer | Building AI agents, intelligent automation & real-world software ","2026-10-02 21:19:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Prudhviraj101\u002FX_Agent --skill internal-comms",{"tool":54,"command":55},"bunx","bunx skills add Prudhviraj101\u002FX_Agent --skill internal-comms",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Prudhviraj101\u002FX_Agent --skill internal-comms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002FSKILL.md",true,[62,68,74,78,82,88,92],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fcomms_brief_template.md","ASSET","资产文件",7286,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Fassets\u002Fcomms_brief_template.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fannouncement_anti_patterns.md","REFERENCE","参考文档",8307,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Freferences\u002Fannouncement_anti_patterns.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fchange_management_canon.md",7479,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Freferences\u002Fchange_management_canon.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Finternal_comms_canon.md",7621,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Freferences\u002Finternal_comms_canon.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fchange_announcement_builder.py","SCRIPT","脚本",14739,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Fscripts\u002Fchange_announcement_builder.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fcomms_calendar_builder.py",11259,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Fscripts\u002Fcomms_calendar_builder.py",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fcomms_template_filler.py",13089,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fbusiness-operations__internal-comms\u002Fscripts\u002Fcomms_template_filler.py",[97,106,114,122,129,137],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DQMKNKM6F5G21PPJNW3HR5","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7DQMF21V9VHCTVS8H5JFNJM","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7DQM8HREQ0DN1HV12K0W3VT","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7DQM5J7B71CQ8EVHBXCCCN2","systematic-planning","Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystematic-planning\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7DQKG6WREWGRRCKHCJS96Y1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7DQJY7AN1XCX6G3ACA5K4JH","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]