Use ai-adoption-rollout

Plan the human rollout of an AI tool or workflow to an organisation

Plan the human rollout of an AI tool or workflow to an organisation — sized cohorts, enablement per cohort, named champions, a comms plan that states what will not change, and an adoption gate every wave must pass before the next one opens.

Reach for it when a tool has been chosen and the question is how it reaches people without stalling or backlash. Do NOT use to phase a technical cutover (that's migration-plan) or to choose which use case to roll out (that's ai-use-case-triage).

Install it

npx skilldrop-cli install ai-adoption-rollout                 # Claude Code, your user folder
npx skilldrop-cli install ai-adoption-rollout --project       # Claude Code, this repo
npx skilldrop-cli install ai-adoption-rollout --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the AI engineering pack: --pack ai-engineering installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Plan how we roll this AI tool out to the org"
• "How do we drive adoption without a backlash?"
• "Design the cohorts and enablement for our AI launch"
• "Our last AI rollout decayed after launch — plan the retry"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Plan the phased migration of our database schema"
• "Which use case should we roll out first?"
• "Write the rules for what people can put into these tools"

If another skill answers instead, ask for this one by name: "use ai-adoption-rollout".

Check what you get

A good result:

• Cohorts get smaller-to-larger with a stated reason each, and the plan refuses a single big-bang wave.
• Every wave has an adoption gate with an observable, a threshold, and a bake time — plus a rollback if it fails.
• The outcome is a behaviour, not a usage number. Licences activated is not adoption.
• The comms plan states explicitly what will not change (headcount, evaluation, how work is judged). Omitting it is a defect, not a tone choice.
• Champions are roles with protected hours, never names, and never unbudgeted.
• Enablement is per cohort and hands-on with the participant's own work — a single deck for everyone is the failure mode.
• The friction loop names an owner and a cadence.

Use something else when

• Phasing a technical cutover (schema, API version, datastore) — that's migration-plan, which sequences systems, not people.
• Choosing which use case to roll out — that's ai-use-case-triage.
• Deciding whether the organisation is ready at all — that's ai-readiness-assessment.
• Writing the rules for what may be put into the tool — that's ai-usage-policy.
• Reporting on adoption that already happened — that's ai-usage-report.

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: ai-readiness-assessment, ai-usage-policy, ai-usage-report, ai-use-case-triage, migration-plan

Edit this page on GitHub · View source