Adoption strategy design producing communication plan, training roadmap, resistance management tactics, and reinforcement mechanisms. Use when the user asks to "design adoption strategy", "plan change adoption", "communication plan", "training needs analysis", "resistance management", "adoption roadmap", "change communication", or mentions "post-implementation adoption", "user onboarding strategy", "technology adoption plan".
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.
Designs a comprehensive adoption strategy: phased rollout plan, stakeholder communication strategy, training needs analysis and curriculum design, resistance management tactics, reinforcement mechanisms, and adoption KPIs with measurement cadence.
Adoption is not an event, it is a process. It does not end at go-live — it begins there. Every user who does not adopt represents an investment that does not return.
$1 — Path to project context (change readiness assessment, solution roadmap, stakeholder map)$2 — Strategy scope: full (default), communication (comms plan only), training (training plan only)Parse from $ARGUMENTS.
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso{FORMATO}: markdown (default) | html | dual | pptx (sponsor presentation){MODO_OPERACIONAL}: estrategia (default, full strategy) | comunicacion (communication plan focus) | capacitacion (training plan focus){VARIANTE}: ejecutiva (~40% — rollout phases + KPIs) | técnica (full, default)Mandatory:
Recommended:
Assumptions:
Cannot do:
| Missing Input | Impact | Workaround |
|---|---|---|
| No readiness assessment | Cannot target interventions | Use stakeholder map + assumptions; flag [SUPUESTO] |
| No solution roadmap | Cannot phase the rollout | Design generic 3-phase rollout; align when roadmap available |
| No training infrastructure | Cannot specify delivery | Recommend low-cost options (peer learning, documentation, recorded sessions) |
| No communication channels | Cannot design distribution | Audit available channels from project artifacts |
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Full strategy | Comprehensive, all stakeholder groups covered | 3-5 days, multiple deliverables | Major transformations, >100 users affected |
| Communication-only | Fast, targeted messaging plan | No training or reinforcement design | When training is handled separately |
| Training-only | Detailed curriculum, materials spec | No communication or rollout strategy | When comms is handled by marketing/comms team |
Change summary, affected stakeholder groups (from readiness assessment), adoption timeline, success definition (quantitative targets: adoption rate %, proficiency %, satisfaction score).
Phased approach: Pilot → Early adopters → Majority → Laggards. Per phase: scope, duration, entry criteria, exit criteria, rollback plan. Wave planning for large organizations.
Per stakeholder group: key messages (why, what, how, when), preferred channels, sender (who delivers the message matters), frequency, feedback mechanism. Communication calendar (Gantt).
Message framework by ADKAR stage:
Per role: current skills, required skills, gap analysis, training method (classroom, e-learning, peer, on-the-job), duration, materials needed. Curriculum map with prerequisites and sequencing.
Per resistance type identified in readiness assessment: tactic, responsible party, timeline. Tactics catalog: education, participation, facilitation, negotiation, co-optation. Escalation path for unresolved resistance.
Champion selection criteria, champion responsibilities, champion enablement plan (train-the-trainer), champion communication cadence, champion recognition/incentive structure.
Post-go-live: coaching plan, help desk/support model, knowledge base maintenance, feedback loops, iteration cadence for process improvements. Sustainability plan (what happens when the project team leaves).
| KPI | Definition | Target | Measurement Method | Cadence | Intervention Threshold | Per KPI: what triggers action, what action is triggered. Dashboard specification.
Core KPIs: adoption rate, proficiency rate, utilization rate, satisfaction (NPS/CSAT), time-to-competency, support ticket volume.
Typical engagement: 3-4 days for transformations affecting <500 users.
Primary: Estrategia_Adopcion_{project}.md (or .html if {FORMATO}=html|dual) — Full 8-section adoption strategy.
Secondary: Plan_Comunicacion_{project}.md — Communication calendar + message templates.
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. |
pptx | On demand | Slide spec for sponsor presentation. |
| Mode | Focus | Best For |
|---|---|---|
estrategia (default) | Full 8-section strategy | Major transformations, Phase 5b deliverable |
comunicacion | S1 + S3 + S6 deep | When training is handled separately |
capacitacion | S1 + S4 + S6 deep | When comms is handled by another team |
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 |
|---|---|
| Adoption is mandatory (compliance-driven) with hard regulatory deadline | Replace incentive-based tactics with compliance deadline milestones; add legal language to communications; require training completion audit trail; build escalation path for non-compliance |
| Global rollout across 5+ time zones and 3+ languages | Create localization matrix per region; adapt messaging for cultural context; use train-the-trainer cascade model; stagger rollout waves by region to absorb lessons learned |
| Champion network cannot be established (no volunteers, no management mandate) | Fall back to "embedded support" model: assign super-users from existing team leads; reduce champion responsibilities to minimum viable (FAQ answering, issue escalation); escalate champion gap to sponsor |
| Change fatigue detected — organization has 3+ concurrent transformation initiatives | Design a lighter-touch strategy that integrates into existing ceremonies (stand-ups, town halls); avoid "another initiative" framing; position as enhancement to current work, not additional burden |
| Decision | Alternativa Descartada | Justificacion |
|---|---|---|
| Phase rollout as Pilot > Early Adopters > Majority > Laggards | Big-bang simultaneous rollout to all users | Phased rollout absorbs lessons from each wave, reduces blast radius of issues, and builds internal success stories that accelerate later waves |
| Communication plan aligned to ADKAR stages (Awareness > Desire > Knowledge > Ability > Reinforcement) | Generic "launch announcement + training" approach | ADKAR-aligned messaging addresses the psychological progression of adoption; generic approaches often skip Desire (motivation) and Reinforcement (sustainability) |
| Every KPI must have an intervention threshold that triggers concrete action | Track KPIs as informational dashboards only | Dashboards without intervention thresholds are measurement theater; the threshold-to-action link is what makes adoption strategy operational |
graph TD
subgraph Core["Adoption Strategy"]
A["Adoption Context"] --> B["Rollout Phases"]
B --> C["Communication Plan"]
B --> D["Training Curriculum"]
C --> E["Resistance Management"]
D --> F["Champion Network"]
E --> G["Reinforcement Mechanisms"]
F --> G
G --> H["Adoption KPIs"]
end
subgraph Inputs["Inputs"]
I["Readiness Assessment"] --> A
J["Solution Roadmap"] --> B
K["Stakeholder Map"] --> C
end
subgraph Outputs["Outputs"]
H --> L["Adoption Strategy Document"]
C --> M["Communication Calendar"]
end
subgraph Related["Related Skills"]
N["change-readiness-assessment"] -.-> I
O["workshop-facilitator"] -.-> D
end
Estrategia_Adopcion_{cliente}_{WIP}.mdEstrategia_Adopcion_{cliente}_{WIP}.pptxEstrategia_Adopcion_{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.