[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF0TNFFA0JQBHNFYYW9WVX":3,"skill-same:01M7AF0TNFFA0JQBHNFYYW9WVX":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF0TNFFA0JQBHNFYYW9WVX","change-management-skill",null,"Organisational change management with stakeholder analysis, communication planning, and adoption tracking. Use when rolling out a new process, a tool migration, or an organisational restructure. Trigger with \"manage change for\", \"change management plan\", \"how do we roll out [change]\".","innFactory-AI\u002Fcompany-ai-stack-skills","innFactory-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165681221?v=4","01M7AEC27VD0D1QX2XBX441MDW","innFactory AI","01M7AEC28G25HQ9H9SN58MNV27",0,"MIT","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Foperations\u002Fchange-management-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: change-management-skill\ndescription: Organisational change management with stakeholder analysis, communication planning, and adoption tracking. Use when rolling out a new process, a tool migration, or an organisational restructure. Trigger with \"manage change for\", \"change management plan\", \"how do we roll out [change]\".\n---\n\n# Change Management Skill\n\nPlan and run organisational change — stakeholder analysis, communication planning, training design, and adoption measurement. The skill carries people and process through the transition, from first announcement to durable embedding.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **HR \u002F org system via MCP** (e.g. HubSpot, Workday, BambooHR) | Team structures, reporting lines, affected roles, contact details |\n| **Project tracker via MCP** (e.g. Asana, Monday, Jira, Notion) | Rollout tasks, milestone status, owner assignments |\n| **companyRAG collections \u002F file upload** | Stakeholder lists, prior change plans, survey results, training materials |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Change Impact Assessment\n\nBefore planning, assess the scope and nature of the change. This determines the intensity of the change management effort.\n\n### Impact Dimensions\n\nScore each dimension from the user's description of the change:\n\n| Dimension | Low Impact | Medium Impact | High Impact |\n| --- | --- | --- | --- |\n| **People affected** | Single team | Multiple teams or department | Cross-functional or organisation-wide |\n| **Process change** | Minor adjustment to existing workflow | New workflow replacing existing one | Fundamental redesign of how work is done |\n| **Technology change** | Update within existing tool | New tool for existing process | New platform changing multiple workflows |\n| **Organisational structure** | Role adjustments within team | Team restructure | Departmental or reporting line changes |\n| **Skills required** | Existing skills sufficient | Moderate upskilling needed | Significant reskilling or new capabilities |\n| **Timeline pressure** | Flexible timeline | Fixed deadline with buffer | Hard deadline, regulatory, or contractual |\n\n### Change Intensity Classification\n\n| Classification | Criteria | Change Management Effort |\n| --- | --- | --- |\n| **Incremental** | Low impact across most dimensions | Lightweight — communication + quick-reference guide |\n| **Transitional** | Medium impact on 2+ dimensions | Moderate — full stakeholder analysis, training plan, adoption tracking |\n| **Transformational** | High impact on 3+ dimensions | Intensive — dedicated change lead, phased rollout, sustained reinforcement |\n\nThe intensity classification determines how deeply to apply each section of this skill. Incremental changes do not require the full methodology; transformational changes require every element.\n\n## Stakeholder Analysis\n\n### Stakeholder Identification\n\nMap all individuals and groups affected by or influencing the change:\n\n| Stakeholder | Role in Change | Impact Level | Influence Level | Current Stance | Desired Stance |\n| --- | --- | --- | --- | --- | --- |\n| [Name\u002FGroup] | Sponsor \u002F Champion \u002F Affected \u002F Blocker | High \u002F Medium \u002F Low | High \u002F Medium \u002F Low | Advocate \u002F Supportive \u002F Neutral \u002F Resistant \u002F Hostile | [target stance] |\n\n### Influence-Impact Matrix\n\nPlot stakeholders on two axes to determine engagement strategy:\n\n|  | High Influence | Low Influence |\n| --- | --- | --- |\n| **High Impact** | **Manage closely** — regular 1:1 engagement, early involvement in design, address concerns proactively | **Keep informed** — regular communication, feedback channels, training priority |\n| **Low Impact** | **Keep satisfied** — periodic updates, consult on decisions within their domain | **Monitor** — general communication, available support |\n\n### Stakeholder Engagement Plan\n\nFor each stakeholder in the \"Manage closely\" and \"Keep informed\" quadrants:\n\n```\nSTAKEHOLDER ENGAGEMENT:\n  Stakeholder:       [name or group]\n  Current stance:    [from identification table]\n  Desired stance:    [target]\n  Key concerns:      [what they stand to lose or fear about the change]\n  Key benefits:      [what they stand to gain — framed in THEIR terms, not the organisation's]\n  Engagement tactic: [specific action — meeting cadence, involvement in design, early access]\n  Owner:             [who is responsible for this stakeholder relationship]\n  Success indicator: [observable behaviour showing stance shift]\n```\n\n## Resistance Diagnosis\n\nResistance is information, not an obstacle. Diagnose the source before designing the response.\n\n### Resistance Source Framework\n\n| Source | Manifestation | Root Cause | Response Strategy |\n| --- | --- | --- | --- |\n| **Lack of awareness** | \"I didn't know this was happening\" | Insufficient communication | Increase visibility — direct communication from sponsor |\n| **Lack of understanding** | \"I don't see why we need this\" | Unclear rationale or business case | Explain the WHY — connect to problems they experience |\n| **Lack of capability** | \"I don't know how to do this\" | Insufficient training or support | Build skills — hands-on training, coaching, job aids |\n| **Lack of willingness** | \"I don't want to do this\" | Personal impact concerns (status, workload, job security) | Address concerns — listen, involve, adapt where possible |\n| **Lack of reinforcement** | \"We tried this before and went back\" | No consequences or incentives for adoption | Sustain — management accountability, recognition, metrics |\n\n### Resistance Response Principles\n\n- Investigate before responding — the presenting objection is rarely the actual concern\n- Never dismiss resistance as irrational — it is rational from the stakeholder's perspective\n- Distinguish between resistance to the change itself and resistance to how the change is being managed\n- Track resistance themes across stakeholders — recurring themes signal systemic issues to address at the programme level, not individual conversations\n\n## Communication Planning\n\n### Communication Architecture\n\nDesign communication by audience, timing, and channel:\n\n| Phase | Timing | Audience | Message Focus | Channel | Owner |\n| --- | --- | --- | --- | --- | --- |\n| **Announce** | Before change begins | All affected | WHY — business case, vision, what's changing | Town hall, email from sponsor | Change sponsor |\n| **Prepare** | Weeks before go-live | Directly affected teams | WHAT — specific impacts, timeline, what to expect | Team meetings, detailed guide | Team leads + change team |\n| **Enable** | At go-live | Users transitioning | HOW — step-by-step guidance, where to get help | Training sessions, quick-reference, helpdesk | Change team + trainers |\n| **Reinforce** | Post go-live | All affected | PROGRESS — wins, feedback incorporation, next steps | Updates, dashboards, recognition | Change team + managers |\n\n### Message Design Principles\n\nFor every communication, answer these questions from the recipient's perspective:\n\n1. What is changing? — concrete description, not abstract vision\n2. Why is it changing? — business rationale connected to a problem they recognise\n3. What does it mean for me? — specific impact on their daily work\n4. What do I need to do? — clear, actionable next steps with dates\n5. Where do I get help? — support channels, contacts, resources\n6. What if I have concerns? — feedback mechanism with genuine response commitment\n\n### Communication Anti-Patterns\n\n| Anti-Pattern | Problem | Better Approach |\n| --- | --- | --- |\n| Leading with technology features | Sounds like a sales pitch, not addressing their concerns | Lead with the problem being solved and the benefit to them |\n| \"Exciting transformation\" language | Feels dismissive of the disruption they experience | Acknowledge the difficulty honestly alongside the rationale |\n| Information-only communication | Tells but doesn't listen — kills trust | Two-way: include feedback mechanisms and respond to input |\n| Communicating too late | Change feels imposed rather than co-created | Front-load awareness; involve early even if details are incomplete |\n| Single-channel broadcast | Misses audiences, feels impersonal | Multi-channel with tailored messaging per audience segment |\n| Silence after launch | Signals abandonment; resistance fills the vacuum | Sustained reinforcement cadence for at least 3-6 months |\n\n## Training Design\n\n### Training Needs Assessment\n\nFor each affected group, assess the gap between current and required capability:\n\n```\nTRAINING NEEDS:\n  Group:                 [team or role]\n  Current capability:    [what they can do today]\n  Required capability:   [what the change requires them to do]\n  Gap:                   [specific skills or knowledge to build]\n  Learning preference:   [hands-on, documentation, coaching — from org knowledge]\n  Constraint:            [time available, location, language, accessibility needs]\n  Training method:       [workshop, e-learning, job aid, peer coaching, shadowing]\n  Timeline:              [when training must complete relative to go-live]\n```\n\n### Training Delivery Principles\n\n- Train as close to go-live as possible — skills decay rapidly if not applied immediately\n- Provide job aids (quick-reference cards, checklists) alongside training — people forget 70%+ within a week without reinforcement\n- Include practice with realistic scenarios, not just feature walkthroughs\n- Designate super-users or floor-walkers for the first weeks post go-live\n- Plan for stragglers — not everyone can attend the initial sessions\n\n## Adoption Tracking\n\n### Adoption Metrics Framework\n\nMeasure adoption across four dimensions:\n\n| Dimension | What It Measures | Example Metrics | Data Source |\n| --- | --- | --- | --- |\n| **Awareness** | Do people know about the change? | Communication reach, survey awareness score | Email analytics, pulse surveys |\n| **Adoption** | Are people using the new way? | System login rates, process compliance rate, old-system usage decline | System analytics, audit data |\n| **Proficiency** | Are people using it correctly? | Error rates, support ticket volume, time-to-complete | System analytics, helpdesk data |\n| **Sustainability** | Is it sticking? | Adoption trend over time, reversion rate, manager reinforcement | Longitudinal tracking |\n\n### Adoption Dashboard Structure\n\n```\nADOPTION DASHBOARD — [Change Name] — [Date]\n\nAwareness:     [metric] — [current value] — [target] — [trend ↑↓→]\nAdoption:      [metric] — [current value] — [target] — [trend ↑↓→]\nProficiency:   [metric] — [current value] — [target] — [trend ↑↓→]\nSustainability: [metric] — [current value] — [target] — [trend ↑↓→]\n\nKey risks:     [top adoption risks with mitigation status]\nActions:       [current and next planned interventions]\n```\n\n### Adoption Stall Diagnosis\n\nWhen adoption plateaus or declines, diagnose by checking each dimension:\n\n- Awareness stable but adoption low → people know but aren't doing → investigate willingness or capability barriers\n- Adoption initially high then declining → novelty wore off, reinforcement failing → check manager accountability and incentives\n- Adoption high but proficiency low → using it but incorrectly → training gap, provide coaching or revised job aids\n- All dimensions low → fundamental change approach issue → revisit stakeholder analysis and communication plan\n\n## Output Template\n\nStructure the final change management plan as follows:\n\n```\n# Change Management Plan — [Change Name]\n\n## Change Overview\n- Description: [what is changing]\n- Business case: [why, connected to organisational strategy]\n- Scope: [who, what, where]\n- Timeline: [key milestones]\n- Change intensity: [Incremental \u002F Transitional \u002F Transformational]\n\n## Stakeholder Analysis\n[Stakeholder map, influence-impact matrix, engagement plans]\n\n## Resistance Assessment\n[Diagnosed resistance sources, response strategies]\n\n## Communication Plan\n[Communication architecture table, key messages by phase]\n\n## Training Plan\n[Training needs per group, delivery schedule, job aids]\n\n## Adoption Metrics\n[Metrics framework, targets, tracking cadence, dashboard]\n\n## Risks and Mitigations\n[Change-specific risks with owners and response plans]\n\n## Governance\n- Change sponsor: [name and role]\n- Change lead: [name]\n- Review cadence: [how often the plan is reviewed and adapted]\n- Escalation path: [how issues are raised and resolved]\n```\n\n## Guardrails\n\n- Never generate organisation-specific culture, politics, or stakeholder dispositions from training data. All organisational context comes from the user.\n- Never fabricate stakeholder names, roles, or relationships. All stakeholder data comes from the user.\n- Never claim \"best practice\" adoption rates or resistance percentages. These vary dramatically by organisation and context.\n- Label generated content: `[From org data]`, `[Framework methodology]`, `[AI suggestion — verify]`.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted plan ready to share.\n","# Change Management Skill\n\nPlan and run organisational change — stakeholder analysis, communication planning, training design, and adoption measurement. The skill carries people and process through the transition, from first announcement to durable embedding.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **HR \u002F org system via MCP** (e.g. HubSpot, Workday, BambooHR) | Team structures, reporting lines, affected roles, contact details |\n| **Project tracker via MCP** (e.g. Asana, Monday, Jira, Notion) | Rollout tasks, milestone status, owner assignments |\n| **companyRAG collections \u002F file upload** | Stakeholder lists, prior change plans, survey results, training materials |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Change Impact Assessment\n\nBefore planning, assess the scope and nature of the change. This determines the intensity of the change management effort.\n\n### Impact Dimensions\n\nScore each dimension from the user's description of the change:\n\n| Dimension | Low Impact | Medium Impact | High Impact |\n| --- | --- | --- | --- |\n| **People affected** | Single team | Multiple teams or department | Cross-functional or organisation-wide |\n| **Process change** | Minor adjustment to existing workflow | New workflow replacing existing one | Fundamental redesign of how work is done |\n| **Technology change** | Update within existing tool | New tool for existing process | New platform changing multiple workflows |\n| **Organisational structure** | Role adjustments within team | Team restructure | Departmental or reporting line changes |\n| **Skills required** | Existing skills sufficient | Moderate upskilling needed | Significant reskilling or new capabilities |\n| **Timeline pressure** | Flexible timeline | Fixed deadline with buffer | Hard deadline, regulatory, or contractual |\n\n### Change Intensity Classification\n\n| Classification | Criteria | Change Management Effort |\n| --- | --- | --- |\n| **Incremental** | Low impact across most dimensions | Lightweight — communication + quick-reference guide |\n| **Transitional** | Medium impact on 2+ dimensions | Moderate — full stakeholder analysis, training plan, adoption tracking |\n| **Transformational** | High impact on 3+ dimensions | Intensive — dedicated change lead, phased rollout, sustained reinforcement |\n\nThe intensity classification determines how deeply to apply each section of this skill. Incremental changes do not require the full methodology; transformational changes require every element.\n\n## Stakeholder Analysis\n\n### Stakeholder Identification\n\nMap all individuals and groups affected by or influencing the change:\n\n| Stakeholder | Role in Change | Impact Level | Influence Level | Current Stance | Desired Stance |\n| --- | --- | --- | --- | --- | --- |\n| [Name\u002FGroup] | Sponsor \u002F Champion \u002F Affected \u002F Blocker | High \u002F Medium \u002F Low | High \u002F Medium \u002F Low | Advocate \u002F Supportive \u002F Neutral \u002F Resistant \u002F Hostile | [target stance] |\n\n### Influence-Impact Matrix\n\nPlot stakeholders on two axes to determine engagement strategy:\n\n|  | High Influence | Low Influence |\n| --- | --- | --- |\n| **High Impact** | **Manage closely** — regular 1:1 engagement, early involvement in design, address concerns proactively | **Keep informed** — regular communication, feedback channels, training priority |\n| **Low Impact** | **Keep satisfied** — periodic updates, consult on decisions within their domain | **Monitor** — general communication, available support |\n\n### Stakeholder Engagement Plan\n\nFor each stakeholder in the \"Manage closely\" and \"Keep informed\" quadrants:\n\n```\nSTAKEHOLDER ENGAGEMENT:\n  Stakeholder:       [name or group]\n  Current stance:    [from identification table]\n  Desired stance:    [target]\n  Key concerns:      [what they stand to lose or fear about the change]\n  Key benefits:      [what they stand to gain — framed in THEIR terms, not the organisation's]\n  Engagement tactic: [specific action — meeting cadence, involvement in design, early access]\n  Owner:             [who is responsible for this stakeholder relationship]\n  Success indicator: [observable behaviour showing stance shift]\n```\n\n## Resistance Diagnosis\n\nResistance is information, not an obstacle. Diagnose the source before designing the response.\n\n### Resistance Source Framework\n\n| Source | Manifestation | Root Cause | Response Strategy |\n| --- | --- | --- | --- |\n| **Lack of awareness** | \"I didn't know this was happening\" | Insufficient communication | Increase visibility — direct communication from sponsor |\n| **Lack of understanding** | \"I don't see why we need this\" | Unclear rationale or business case | Explain the WHY — connect to problems they experience |\n| **Lack of capability** | \"I don't know how to do this\" | Insufficient training or support | Build skills — hands-on training, coaching, job aids |\n| **Lack of willingness** | \"I don't want to do this\" | Personal impact concerns (status, workload, job security) | Address concerns — listen, involve, adapt where possible |\n| **Lack of reinforcement** | \"We tried this before and went back\" | No consequences or incentives for adoption | Sustain — management accountability, recognition, metrics |\n\n### Resistance Response Principles\n\n- Investigate before responding — the presenting objection is rarely the actual concern\n- Never dismiss resistance as irrational — it is rational from the stakeholder's perspective\n- Distinguish between resistance to the change itself and resistance to how the change is being managed\n- Track resistance themes across stakeholders — recurring themes signal systemic issues to address at the programme level, not individual conversations\n\n## Communication Planning\n\n### Communication Architecture\n\nDesign communication by audience, timing, and channel:\n\n| Phase | Timing | Audience | Message Focus | Channel | Owner |\n| --- | --- | --- | --- | --- | --- |\n| **Announce** | Before change begins | All affected | WHY — business case, vision, what's changing | Town hall, email from sponsor | Change sponsor |\n| **Prepare** | Weeks before go-live | Directly affected teams | WHAT — specific impacts, timeline, what to expect | Team meetings, detailed guide | Team leads + change team |\n| **Enable** | At go-live | Users transitioning | HOW — step-by-step guidance, where to get help | Training sessions, quick-reference, helpdesk | Change team + trainers |\n| **Reinforce** | Post go-live | All affected | PROGRESS — wins, feedback incorporation, next steps | Updates, dashboards, recognition | Change team + managers |\n\n### Message Design Principles\n\nFor every communication, answer these questions from the recipient's perspective:\n\n1. What is changing? — concrete description, not abstract vision\n2. Why is it changing? — business rationale connected to a problem they recognise\n3. What does it mean for me? — specific impact on their daily work\n4. What do I need to do? — clear, actionable next steps with dates\n5. Where do I get help? — support channels, contacts, resources\n6. What if I have concerns? — feedback mechanism with genuine response commitment\n\n### Communication Anti-Patterns\n\n| Anti-Pattern | Problem | Better Approach |\n| --- | --- | --- |\n| Leading with technology features | Sounds like a sales pitch, not addressing their concerns | Lead with the problem being solved and the benefit to them |\n| \"Exciting transformation\" language | Feels dismissive of the disruption they experience | Acknowledge the difficulty honestly alongside the rationale |\n| Information-only communication | Tells but doesn't listen — kills trust | Two-way: include feedback mechanisms and respond to input |\n| Communicating too late | Change feels imposed rather than co-created | Front-load awareness; involve early even if details are incomplete |\n| Single-channel broadcast | Misses audiences, feels impersonal | Multi-channel with tailored messaging per audience segment |\n| Silence after launch | Signals abandonment; resistance fills the vacuum | Sustained reinforcement cadence for at least 3-6 months |\n\n## Training Design\n\n### Training Needs Assessment\n\nFor each affected group, assess the gap between current and required capability:\n\n```\nTRAINING NEEDS:\n  Group:                 [team or role]\n  Current capability:    [what they can do today]\n  Required capability:   [what the change requires them to do]\n  Gap:                   [specific skills or knowledge to build]\n  Learning preference:   [hands-on, documentation, coaching — from org knowledge]\n  Constraint:            [time available, location, language, accessibility needs]\n  Training method:       [workshop, e-learning, job aid, peer coaching, shadowing]\n  Timeline:              [when training must complete relative to go-live]\n```\n\n### Training Delivery Principles\n\n- Train as close to go-live as possible — skills decay rapidly if not applied immediately\n- Provide job aids (quick-reference cards, checklists) alongside training — people forget 70%+ within a week without reinforcement\n- Include practice with realistic scenarios, not just feature walkthroughs\n- Designate super-users or floor-walkers for the first weeks post go-live\n- Plan for stragglers — not everyone can attend the initial sessions\n\n## Adoption Tracking\n\n### Adoption Metrics Framework\n\nMeasure adoption across four dimensions:\n\n| Dimension | What It Measures | Example Metrics | Data Source |\n| --- | --- | --- | --- |\n| **Awareness** | Do people know about the change? | Communication reach, survey awareness score | Email analytics, pulse surveys |\n| **Adoption** | Are people using the new way? | System login rates, process compliance rate, old-system usage decline | System analytics, audit data |\n| **Proficiency** | Are people using it correctly? | Error rates, support ticket volume, time-to-complete | System analytics, helpdesk data |\n| **Sustainability** | Is it sticking? | Adoption trend over time, reversion rate, manager reinforcement | Longitudinal tracking |\n\n### Adoption Dashboard Structure\n\n```\nADOPTION DASHBOARD — [Change Name] — [Date]\n\nAwareness:     [metric] — [current value] — [target] — [trend ↑↓→]\nAdoption:      [metric] — [current value] — [target] — [trend ↑↓→]\nProficiency:   [metric] — [current value] — [target] — [trend ↑↓→]\nSustainability: [metric] — [current value] — [target] — [trend ↑↓→]\n\nKey risks:     [top adoption risks with mitigation status]\nActions:       [current and next planned interventions]\n```\n\n### Adoption Stall Diagnosis\n\nWhen adoption plateaus or declines, diagnose by checking each dimension:\n\n- Awareness stable but adoption low → people know but aren't doing → investigate willingness or capability barriers\n- Adoption initially high then declining → novelty wore off, reinforcement failing → check manager accountability and incentives\n- Adoption high but proficiency low → using it but incorrectly → training gap, provide coaching or revised job aids\n- All dimensions low → fundamental change approach issue → revisit stakeholder analysis and communication plan\n\n## Output Template\n\nStructure the final change management plan as follows:\n\n```\n# Change Management Plan — [Change Name]\n\n## Change Overview\n- Description: [what is changing]\n- Business case: [why, connected to organisational strategy]\n- Scope: [who, what, where]\n- Timeline: [key milestones]\n- Change intensity: [Incremental \u002F Transitional \u002F Transformational]\n\n## Stakeholder Analysis\n[Stakeholder map, influence-impact matrix, engagement plans]\n\n## Resistance Assessment\n[Diagnosed resistance sources, response strategies]\n\n## Communication Plan\n[Communication architecture table, key messages by phase]\n\n## Training Plan\n[Training needs per group, delivery schedule, job aids]\n\n## Adoption Metrics\n[Metrics framework, targets, tracking cadence, dashboard]\n\n## Risks and Mitigations\n[Change-specific risks with owners and response plans]\n\n## Governance\n- Change sponsor: [name and role]\n- Change lead: [name]\n- Review cadence: [how often the plan is reviewed and adapted]\n- Escalation path: [how issues are raised and resolved]\n```\n\n## Guardrails\n\n- Never generate organisation-specific culture, politics, or stakeholder dispositions from training data. All organisational context comes from the user.\n- Never fabricate stakeholder names, roles, or relationships. All stakeholder data comes from the user.\n- Never claim \"best practice\" adoption rates or resistance percentages. These vary dramatically by organisation and context.\n- Label generated content: `[From org data]`, `[Framework methodology]`, `[AI suggestion — verify]`.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted plan ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Foperations\u002Fchange-management-skill","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills","https:\u002F\u002Fgithub.com\u002FinnFactory-AI","https:\u002F\u002Finnfactory.ai","Engineering AI. Enabling Tomorrow.","2026-11-13 19:54:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill change-management-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill change-management-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill change-management-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Foperations\u002Fchange-management-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill","Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with \"create a one-pager for\", \"sales deck for [deal]\", \"customise this asset for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AF4D32V0FJE0QGCBZSQ7BW","pipeline-review-skill","Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with \"review my pipeline\", \"pipeline health check\", \"deal risk analysis\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fpipeline-review-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AF48W7G8DMAHRAM125B192","outreach-skill","Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with \"draft outreach to [person\u002Fcompany]\", \"write cold email to\", \"outreach sequence for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AF43VKNPQ7G1NTQ4MRH40J","forecast-skill","Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with \"build forecast\", \"forecast for this quarter\", \"where do I stand against quota\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fforecast-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AF3Z5N61VYSEJRYWXR4JP1","deal-strategy-skill","Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with \"plan deal strategy for\", \"stakeholder map\", \"how do I advance this deal\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fdeal-strategy-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill","Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with \"summarise this call\", \"call notes from\", \"write follow-up for this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[]]