[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSZXVMNB2G9QWGG9FGP3SK":3,"skill-same:01M7CSZXVMNB2G9QWGG9FGP3SK":95},{"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":6,"updatedAt":46,"install":47,"resources":60},"01M7CSZXVMNB2G9QWGG9FGP3SK","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\".","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-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","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill internal-comms",{"tool":53,"command":54},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill internal-comms",{"tool":56,"command":57},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill internal-comms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002FSKILL.md",true,[61,67,73,77,81,87,91],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Fcomms_brief_template.md","ASSET","资产文件",7286,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Fassets\u002Fcomms_brief_template.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fannouncement_anti_patterns.md","REFERENCE","参考文档",8307,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Freferences\u002Fannouncement_anti_patterns.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fchange_management_canon.md",7479,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Freferences\u002Fchange_management_canon.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Finternal_comms_canon.md",7621,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Freferences\u002Finternal_comms_canon.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fchange_announcement_builder.py","SCRIPT","脚本",14739,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Fscripts\u002Fchange_announcement_builder.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fcomms_calendar_builder.py",11259,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Fscripts\u002Fcomms_calendar_builder.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fcomms_template_filler.py",13089,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fbusiness-operations\u002Finternal-comms\u002Fscripts\u002Fcomms_template_filler.py",[96,103,110,117,124,131],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]