Free. Built on thirty years of field work. Designed to do the change program right.
A change management methodology plugin for Cowork, Anthropic's agentic desktop application. Produces stakeholder analysis, communications, training, readiness planning, and go-live preparation, with Ignite's structural intent embedded throughout and the limit named in every output.
Most change management programs fail for the same reason: nobody redesigned the conditions. The communications went out. The training sessions were attended. The completion rates looked fine. Six months later, half the organization was working around the new system instead of in it. This plugin produces the change program faster and more structurally than any tool currently available in the Cowork ecosystem. Every output also names exactly what it cannot tell you.
Beyond the change program is environment design, the discipline of engineering the environment so that new behavior becomes the path of least resistance. That discipline requires a different instrument. That instrument is Ignite Spark. This plugin and Spark are designed to work together. This one builds the floor. Spark builds what makes the floor hold.
This plugin is a methodology tool for change management practitioners. It produces structured drafts to support professional judgment, not to replace it.
This plugin is not designed for and should not be used for:
- Evaluating, scoring, or diagnosing individual employees
- HR documentation, performance management, or employment decisions
- Documenting compliance with regulatory, legal, or contractual change management requirements
- Serving as evidence of program completion in audits, litigation, or organizational reviews
- Engagements where no qualified change management practitioner is reviewing and applying the outputs
All outputs are practitioner drafts. They reflect the inputs provided at the time of generation. They require professional review and judgment before use in any engagement context.
Resistance diagnoses characterize behavioral patterns at the role or group level. They do not evaluate individuals and should never be used in connection with individual performance or employment decisions.
Ignite does not collect engagement data through this plugin. Infrastructure-level data practices are governed by Anthropic's platform policies.
Add this plugin from GitHub:
Cowork: Customize > "+" > Add marketplace from GitHub > enter ignite-consulting/change-management
Claude Code:
claude plugins add ignite-consulting/change-managementExplicit workflows you invoke with a slash command:
| Command | Description |
|---|---|
/ocm:start |
Orientation guide: three questions, one starting command, your next sequence. Produces an Artifact Index and optional Terminology Register |
/ocm:workplan |
Change program work plan across three phases (Days 1-30, 30-90, 90+) |
/ocm:milestone-timeline |
Dated T-minus schedule anchored to governance gates and readiness staging |
/ocm:governance-gates |
Seven-gate SteerCo decision model with evidence packages and go/no-go criteria |
/ocm:stakeholder-map |
Stakeholder and sponsor analysis with structural authority assessment |
/ocm:impact-analysis |
Change impact assessment with structural risk identification |
/ocm:comms-plan |
Role-based communications strategy and message architecture |
/ocm:training-plan |
Role-based training strategy with the Tomorrow Test applied |
/ocm:readiness-map |
Day One Readiness Map with go/no-go criteria |
/ocm:readiness-dashboard |
Six-metric quantitative readiness tracking dashboard |
/ocm:resistance-diagnosis |
Resistance analysis with category-specific intervention design |
/ocm:sponsor-brief |
Sponsor activation brief with structural decision register |
/ocm:go-live-checklist |
Go-live readiness checklist with structural condition verification |
/ocm:decision-register |
Live decision register with training and readiness dependency tracking |
/ocm:behavioral-checklist |
Behavioral evidence checklist at the role level |
/ocm:champion-escalation |
Structural escalation package for sponsor-level decision |
/ocm:dependency-map |
Critical path from open decisions to go-live readiness |
/ocm:engagement-close |
Engagement close confirmation for structural engagements |
/ocm:structural-assessment |
Structural readiness profile and pathway to Ignite Spark |
/ocm:session-export |
Export practitioner profile, artifact status, and key decisions as a portable block for new sessions |
New to the plugin? Start with /ocm:start. It will orient you to the right command for your situation in three questions.
Domain knowledge Claude uses automatically when relevant:
| Skill | Description |
|---|---|
change-theory-foundation |
Core methodology: behavior follows structure, two levels of change work, output rules, retired terms, language standards |
change-impact-risk |
Change impact assessment, structural risk identification, three-category resistance diagnosis |
communications-design |
Message design, sender strategy, closed path communications, structural credibility test |
readiness-assessment |
Day One readiness mapping, two-dimension readiness framework, go/no-go decision structure |
stakeholder-sponsor-intelligence |
Four-dimension stakeholder analysis, sponsor identification, engagement approach by category |
sustainment-adoption |
Post-go-live structural condition audits, change agent network design, adoption vs. structural metrics |
training-competency-design |
Tomorrow Test, role-first training design, closed path modules, validation criteria |
/ocm:start
Three questions, one starting command, a recommended sequence. Captures your engagement context (client org, go-live date, deployment model, terminology preferences) so every subsequent command uses it.
We are rolling out a new ERP system across three business units. Finance, Supply Chain, and HR are all affected. The CFO is the executive sponsor. Run /ocm:stakeholder-map for this transformation.
Produces a stakeholder map with structural authority assessment, influence mapping, and engagement approach recommendations.
Our field technicians are resisting the new mobile work order system. They say it takes longer than the paper forms and their supervisors are not enforcing use. Run /ocm:resistance-diagnosis.
Categorizes resistance (structural vs. legitimate concern vs. personal transition) and maps a different intervention to each category.
We are eight weeks from go-live on a new CRM platform. Sales, Customer Service, and Marketing are the impacted populations. Training is 60% complete. Run /ocm:readiness-dashboard.
Six-metric readiness tracking dashboard in Excel. Surfaces gaps between activity readiness and structural readiness.
See CONNECTORS.md for setup requirements and the full list of supported integrations.
Connect your tools for a richer experience:
| Category | Connector | What It Enables |
|---|---|---|
| Project tracker | Notion | Live decision registers, dependency maps, behavioral checklists, champion escalation logs |
| Document storage | SharePoint | Deliverable storage for stakeholder maps, comms plans, training plans, readiness artifacts |
| Communication | Teams | Escalation flags, training blocker alerts, go/no-go status updates |
Every command works standalone (describe your engagement, get the deliverable). Connectors add storage and notification.
This plugin is a methodology assistant for change management practitioners. It structures analysis and generates draft outputs based entirely on information you provide. It does not independently assess organizations or employees, and it does not collect or monitor data about employees or workplace behavior.
All outputs are draft analyses intended for practitioner review. You are responsible for interpreting the output, validating conclusions, and determining any organizational action. All analysis remains at the organizational, role, process, or workstream level.
Built on Anthropic's EU AI Act-compliant Claude platform. Operates as a minimal-risk workflow tool under the Act's risk-based classification framework. Full human oversight at every step, with no autonomous decision-making affecting fundamental rights.
The plugin does not respond to my message. The skill triggers on change management language. If your message does not include terms like "change management," "OCM," "stakeholder," "readiness," "go-live," "resistance," or "adoption," reframe your request using change management terminology.
Outputs feel generic or lack structural framing.
Run /ocm:start first. The practitioner profile captures your engagement context and every subsequent command uses it.
The terminology in the output does not match my client's language.
During /ocm:start, opt in to the terminology alignment exercise. This produces a Terminology Register that all outputs apply silently.
I hit a "limit statement" and do not know what to do with it.
Working as designed. The limit names the boundary between what the change program can produce and what environment design produces. Run /ocm:structural-assessment for a diagnostic, then contact Ignite at https://igniteNA.com for advisory support.
A command produces a .docx but I expected .xlsx (or vice versa). Each command has a fixed output format. Narrative deliverables produce Word documents. Tracking artifacts produce Excel spreadsheets.
My session is getting long and outputs are becoming inconsistent.
Run /ocm:session-export to capture your context as a portable block. Start a new session, paste the export, and say "restore my session context."
This plugin is free to install and use. See LICENSE for full terms. The methodology and structural framing are proprietary to Ignite Consulting.
Ignite Consulting is a boutique transformation firm operating at two levels: the change program (the full OCM delivery layer with structural intent embedded throughout) and environment design (redesigning the conditions so the new way of working holds after the consulting team leaves).
This plugin delivers the change program. Ignite Spark delivers the environment design work beyond it.
Questions, escalations, and Spark access: https://igniteNA.com