Organizational change readiness assessment producing readiness scorecard, resistance map, and intervention plan. Use when the user asks to "assess change readiness", "evaluate organizational readiness", "change impact analysis", "resistance mapping", "ADKAR assessment", "readiness scorecard", or mentions "Phase 5b", "adoption risk", "organizational capacity for change".
From maonpx claudepluginhub javimontano/mao-discovery-frameworkThis skill is limited to using the following tools:
examples/README.mdexamples/sample-output.htmlexamples/sample-output.mdprompts/metaprompts.mdprompts/use-case-prompts.mdreferences/body-of-knowledge.mdreferences/knowledge-graph.mmdreferences/state-of-the-art.mdEnables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Generates a structured organizational readiness evaluation: stakeholder impact analysis, ADKAR-based readiness scoring, resistance heat map, change capacity assessment, and prioritized intervention plan.
You cannot adopt what you do not understand, and you cannot understand what you have not diagnosed. Resistance to change is not the enemy — it is information.
$1 — Path to project context (discovery artifacts, stakeholder maps, org charts)$2 — Assessment scope: full (default), pulse (quick check), continuous (periodic)Parse from $ARGUMENTS.
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso{FORMATO}: markdown (default) | html | dual{MODO_OPERACIONAL}: diagnostico (default, full assessment) | rapido (quick pulse check, 5 dimensions only) | continuo (periodic re-assessment with delta tracking){VARIANTE}: ejecutiva (~40% — scorecard + top interventions) | técnica (full, default)Mandatory:
Recommended:
Assumptions:
Cannot do:
| Missing Input | Impact | Workaround |
|---|---|---|
| No stakeholder map | Cannot segment readiness | Infer from org chart + project RACI; flag as [INFERENCIA] |
| No change description | Cannot assess impact | Use solution roadmap or AS-IS delta; flag scope |
| No historical data | Cannot benchmark | Use industry benchmarks (Prosci data); flag as [SUPUESTO] |
| No org chart | Cannot map cascade | Use project team structure as proxy |
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Full ADKAR assessment | Granular dimension scoring, targeted interventions | 3-5 days, requires stakeholder access | High-impact transformation, regulated environments |
| Quick pulse (rapido) | Fast signal, trend tracking | Misses nuance, no intervention plan | Periodic check-ins, early project phases |
| Continuous tracking | Trend visibility, early warning | Ongoing effort, survey fatigue risk | Multi-phase transformations >6 months |
Scope definition: what is changing (technology, process, roles, culture). Impact matrix by stakeholder group. Change magnitude assessment (incremental → transformational scale 1-5).
Per stakeholder group, score 1-5 on each ADKAR dimension:
Barrier point = lowest-scoring dimension per group. Composite readiness score.
Per stakeholder group: resistance level (1-5), resistance type (cognitive, emotional, behavioral, political), root causes, observable indicators. Heat map visualization (group x dimension).
Organization-level evaluation: concurrent change load, change history (success rate), leadership alignment, communication infrastructure, training capacity, budget for change management.
Top risks to adoption: probability x impact. Per risk: category (people, process, technology, timing), current mitigations, recommended interventions.
Per barrier point identified in S2: targeted intervention, delivery mechanism, timeline, responsible party, success metric. Prioritized by: impact x feasibility.
KPIs for tracking readiness over time: adoption rate, proficiency rate, utilization rate, satisfaction score. Measurement cadence. Dashboard specification.
Typical engagement: 2-3 days for organizations with <500 affected stakeholders.
Primary: Evaluacion_Readiness_{project}.md (or .html if {FORMATO}=html|dual) — Full 7-section readiness assessment with ADKAR scorecards, resistance heat map, and intervention plan.
Secondary: Readiness_Scorecard_{project}.md — Executive summary (S2 composite scores + top 3 interventions).
Included diagrams:
| Format | Default | Description |
|---|---|---|
markdown | ✅ | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
| Mode | Focus | Best For |
|---|---|---|
diagnostico (default) | Full 7-section assessment | Pre-transformation, Phase 5b |
rapido | S1 + S2 + S3 only, simplified scoring | Pulse checks, early phases |
continuo | Delta tracking vs. previous assessment, trend analysis | Multi-phase programs |
Read ${CLAUDE_SKILL_DIR}/references/knowledge-graph.mmd — Domain knowledge graphRead ${CLAUDE_SKILL_DIR}/references/body-of-knowledge.md — Academic and industry sourcesRead ${CLAUDE_SKILL_DIR}/references/state-of-the-art.md — Trends 2024-2026Read ${CLAUDE_SKILL_DIR}/examples/sample-output.md — Golden reference outputRead ${CLAUDE_SKILL_DIR}/examples/sample-output.html — Branded HTMLRead ${CLAUDE_SKILL_DIR}/prompts/use-case-prompts.md — Ready-to-use promptsRead ${CLAUDE_SKILL_DIR}/prompts/metaprompts.md — Meta-strategies| Caso | Estrategia de Manejo |
|---|---|
| Organization undergoing simultaneous M&A and technology transformation | Produce dual-org ADKAR scorecards (acquiring + acquired entity); create a combined view with weighted averages; flag culture clash as a dedicated risk dimension |
| ADKAR scores are uniformly low (<2) across all stakeholder groups | Escalate to executive sponsor immediately; recommend a "readiness sprint" (4-6 weeks) before proceeding with transformation; the organization is not ready to absorb the change |
| Change readiness assessment requested but no stakeholder map exists | Infer stakeholder groups from org chart, project RACI, or solution roadmap team section; tag all groupings as [INFERENCIA]; recommend stakeholder mapping as a prerequisite |
| Assessment reveals executive sponsor is the primary source of resistance | Document the finding with observable indicators only (not personal judgments); escalate to the next governance level; recommend executive coaching or sponsor replacement as intervention options |
| Decision | Alternativa Descartada | Justificacion |
|---|---|---|
| Use ADKAR as the primary readiness framework | Kotter 8-Step or Lewin 3-Phase models | ADKAR provides per-dimension scoring at the individual/group level, enabling targeted interventions; Kotter and Lewin are organizational-level and harder to operationalize for specific barrier points |
| Measure readiness at stakeholder-group level, not individual level | Individual-level assessment for every affected person | Individual assessment does not scale beyond 50 people; group-level patterns are sufficient for intervention design and respect assessment effort constraints |
| Require observable indicators for every ADKAR score | Allow self-reported readiness surveys as primary evidence | Self-reported readiness suffers from social desirability bias; observable indicators (attendance, participation, skill demonstrations) provide more reliable data |
graph TD
subgraph Core["Change Readiness Assessment"]
A["Change Impact Profile"] --> B["ADKAR Scorecard"]
B --> C["Resistance Heat Map"]
C --> D["Intervention Plan"]
D --> E["Measurement Framework"]
end
subgraph Inputs["Inputs"]
F["Stakeholder Map"] --> A
G["Change Description"] --> A
H["Historical Change Data"] --> B
end
subgraph Outputs["Outputs"]
E --> I["Readiness Report"]
D --> J["Executive Scorecard"]
end
subgraph Related["Related Skills"]
K["adoption-strategy"] -.-> D
L["solution-roadmap"] -.-> A
M["user-representative"] -.-> B
end
Evaluacion_Readiness_{cliente}_{WIP}.mdEvaluacion_Readiness_{cliente}_{WIP}.pptxEvaluacion_Readiness_{cliente}_{WIP}.html{fase}_{entregable}_{cliente}_{WIP}.docx{fase}_{entregable}_{cliente}_{WIP}.xlsx| Dimension | Peso | Criterio |
|---|---|---|
| Trigger Accuracy | 10% | Descripcion activa triggers correctos sin falsos positivos |
| Completeness | 25% | Todos los entregables cubren el dominio sin huecos |
| Clarity | 20% | Instrucciones ejecutables sin ambiguedad |
| Robustness | 20% | Maneja edge cases y variantes de input |
| Efficiency | 10% | Proceso no tiene pasos redundantes |
| Value Density | 15% | Cada seccion aporta valor practico directo |
Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.