18 Claude Skills for Digital Transformation

Use when: You need a structured fact base on where the client sits across technology, data, talent, and culture before setting ambitions

Output: Five-domain maturity profile, gap narrative, and top three priority findings

Use when: You need to understand what the client owns before deciding what to build, buy, or retire

Output: Application portfolio map with TIME labels, redundancy register, gap list, and rationalization priority list

Use when: Leadership ambitions outpace what you observe on the ground, or a previous transformation stalled without a diagnosed root cause

Output: Six-dimension readiness scorecard, red flags, precondition recommendations, and overall readiness verdict

Use when: The client needs to move from 'we need to be more digital' to a strategy with real choices and priorities

Output: Transformation thesis, ambition statement, three-horizon where-to-play choices, and critical bets

Use when: A long list of digital ideas needs to be ranked and sequenced before the roadmap can be built

Output: Scored use case register, 2x2 prioritization matrix, three-wave plan, and top-10 rationale memo

Use when: An initiative needs a business case to survive CFO or board scrutiny, or an existing case is too optimistic

Output: Strategic rationale, quantified benefit register with driver logic, cost estimate, NPV and payback for three scenarios, and risk-adjusted recommendation

Use when: The client has a digital strategy but no plan for how the organization will deliver and sustain it

Output: Recommended organizational archetype with rationale, governance and decision rights matrix, ways of working blueprint, and transition plan

Use when: The team is underestimating the capability investment required, or strategy assumptions about talent and process are vague

Output: Capability requirements by pillar, gap register with human/process/technology breakdown, build/buy/partner options, and capability roadmap

Use when: A technology or process plan exists but there is no corresponding plan for how people will be prepared and supported

Output: Change impact heat map, stakeholder engagement plan, communication calendar, capability building plan, and adoption metrics

Use when: Technical debt or overlapping systems have been identified and the client needs a sequenced plan to address them without disrupting operations

Output: Retirement plan, consolidation plan with migration approach, modernization approach for load-bearing systems, dependency sequence, and 18-month roadmap

Use when: Multiple digital use cases depend on data that does not exist in a usable form, or a previous data lake investment delivered no value

Output: Data ambition statements, critical data asset register with gap assessment, governance model, analytics maturity targets, and data capability roadmap

Use when: The client has decided to move to cloud and needs a migration sequence, not a vendor pitch

Output: Workload classification by migration approach (6 Rs), dependency map, wave plan, risk register, and landing zone checklist

Use when: A transformation program is being set up and needs a governance structure, or an existing program is stalling because decision rights are unclear

Output: Three-tier governance structure, RACI for top 12 decisions, cadence calendar, escalation protocol, and program structure charter

Use when: A program is rushing to start building before the environment, team, and standards are ready

Output: Six-track Sprint Zero plan, roles and access checklist, architecture decision record list, backlog readiness checklist, and Sprint Zero calendar

Use when: The program lacks a measurement system or reported metrics are activity metrics rather than outcome metrics

Output: Program outcome statements, three-level KPI hierarchy, measurement methodology, value tracking cadence, and quarterly value realization report template

Use when: The transformation story must land in a leadership meeting and the current version reads like a technology briefing rather than a business case

Output: SCQA narrative spine, Pyramid structure with key messages, hostile Q&A with five responses, and 60-second opening draft

Use when: Specific leaders are creating friction but the team does not have a clear view of why, or generic communication is not working

Output: Stakeholder map with stances, resistance diagnosis by type, targeted engagement plan, coalition design, and 30-day engagement priority list

Use when: The transformation is going to the board for approval and the team needs a presentation architecture designed for a board decision, not a project update

Output: Slide-by-slide architecture for a 10-11 slide board deck, appendix structure, pre-briefing plan, decision statement, and opening paragraph draft