Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/change-management-plan
Create a structured change management plan for any organisational change.
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
and 18 more in the full report
13 fixed4 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a full change management plan for rolling out Salesforce across our regional sales team. We have 150 reps in 4 offices transitioning from legacy spreadsheets over the next 3 months. Our CRO is sponsoring this initiative, and the main concern is reps fearing extra administrative overhead. Please organize the strategy covering the current/future state transition, stakeholder mapping, impact analysis, communication schedule, pre-launch training details, tactics for managing resistance, and long-term adoption metrics.
| Checked | Without skill | With skill |
|---|---|---|
| Includes header metadata fields for sponsor, manager, go-live date, and affected population. | Missed | Passed |
| Includes an explicit subsection specifying what stays the same for employees. | Missed | Passed |
| Includes a stakeholder analysis table containing group size, impact level, current sentiment, and required needs. | Missed | Passed |
The instructions your model reads when the skill loads.
Produces a structured change management plan — because most change initiatives fail not because the change is wrong, but because people aren't brought along with it.
Ask the user for these if not provided:
Change sponsor: [Executive owner] Change manager: [Who is running this] Go-live date: [Date] Affected population: [N people, N teams/locations]
From (current state): [Specific description of today's situation] To (future state): [Specific description of what changes] Why this change is happening: [Honest explanation — people adopt change faster when they understand the real reason] What stays the same: [Explicitly naming what is NOT changing reduces anxiety]
| Stakeholder group | Size | Impact level | Current sentiment | What they need |
|---|
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.