Activates when the conversation involves readiness assessment, go-live planning, Day One preparation, risk identification, go/no-go decisions, or questions about whether an organization is prepared to launch. Trigger phrases include "readiness assessment", "go/no-go", "Day One readiness", "are we ready", "readiness map", "go-live risk", "launch readiness", "cutover", "readiness checklist", "who decides if we go live".
From change-managementnpx claudepluginhub anthropics/claude-plugins-community --plugin change-management-pluginThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Readiness has two dimensions. Both must appear in any readiness assessment. Neither substitutes for the other.
Activity readiness confirms whether the change program work is complete: training delivered, communications sent, support structure in place, change agents activated, documentation accessible, help desk prepared. Activity readiness is necessary. It is not sufficient.
Structural readiness confirms whether the structural conditions are in place: closed paths confirmed and active, accountability structure activated, measurement systems configured for the new state, decision authority confirmed for go-live exceptions, escalation path defined and tested. Structural readiness is the condition that determines whether activity readiness produces transformation or produces compliance that reverts.
A go/no-go decision based on activity readiness alone is a decision based on half the picture.
The Day One Readiness Map is the primary readiness instrument. It answers, role by role and process by process: what must execute on day one, in which system, with what support, and what can no longer be done?
The map has five elements per role:
The go/no-go decision is a formal plan element. It has three required components:
Criteria,specific, binary conditions that must be true for go-live to proceed. Not "training is substantially complete." The specific percentage, by role group, required to proceed, and what happens to the population that has not completed by that threshold.
Decision authority,one named person who owns the go/no-go call. Not a steering committee. Not a consensus process. One person with the structural authority to hold the date or push it, and who has confirmed they will make that call.
Escalation path,if the criteria are not met by the decision window, the escalation path names who is notified, what the options are, and what the timeline for a revised decision looks like.
A go/no-go process without a named decision authority is not a process. It is a report.
Readiness assessment confirms whether change program activities are complete and structural conditions are in place at a point in time. It does not assess whether those structural conditions will hold after go-live without consulting presence. The most important structural readiness question, whether the organization can sustain the new state on its own, is answered through ongoing monitoring, not a pre-launch assessment.