22 AI Skills That Rebuild a $1.5M Transformation Methodology

Act as a senior competitive intelligence analyst.

From the attached competitor list, earnings call transcripts,
press releases, job postings and analyst reports, produce:

1. Shipped versus announced: what each competitor has actually
   put into production, as opposed to what it has announced
2. The gap analysis against our current position
3. Two recommended competitive moves, with rationale

Act as a disciplined program director.

From the flagship use case, the team's capacity, the timeline
and the success criteria leadership expects, produce a one-page
scoping document:

1. In scope / out of scope: explicit lines, no grey zone
2. The time box: a firm pilot duration
3. The stop criteria: the exact conditions that end the pilot,
   no matter the enthusiasm

Act as an organizational strategist.

From the attached org chart, pilot scope, meeting notes and
budget context, produce:

1. A political RACI that reflects the reality of power, not
   the official org chart
2. Identification, with rationale: the real sponsor, the
   declared blockers, the silent killers, the swing votes
   and the operational allies

Act as a change management specialist.

From the pilot scope, the stakeholder map, the engagement
surveys and the post-mortems of past change initiatives,
produce:

1. The leadership air-cover assessment: real support, not
   stated support
2. The middle-management fear analysis: where and why
3. The frontline adoption signal: who will get on board,
   who will resist
4. The three priority interventions to raise the odds
   of success

Act as an operational governance designer.

From the target operating model, the org chart and the
proposed workflow, produce:

1. The list of every decision point in the workflow
2. For each decision: a single named owner, not a committee
3. An SLA per decision: the maximum response time
4. The fallback authority if the owner does not decide
   within the deadline

Act as an operations process designer.

From the target operating model and the human-in-the-loop
protocol, produce a three-tier escalation structure:

1. For each tier: the exact triggers that escalate a case
2. The receiver of each tier: role and person
3. The pickup SLA per tier
4. The documentation requirements at every escalation

Act as a neutral technology procurement advisor.

From the build-or-buy decision, the target operating model
and the vendor capability and pricing data, produce:

1. A comparison matrix: capabilities, lock-in risk,
   integration burden, 3-year total cost
2. Flags on risky contract clauses
3. A firm recommendation, with rationale

Act as a transformation portfolio director.

From the flagship pilots, the stakeholder map, the
change-readiness audit and the architecture audit, produce:

1. A three-pilot sequence, with the rationale for the order
2. The political dependencies: who must succeed before whom
3. The technical dependencies: which foundations each pilot
   requires
4. The roadmap dominoes: what each success unlocks next

Act as a program director.

From the pilot scoping and the operating model, draft a
formal charter in six sections:

1. Scope
2. Measurable success criteria
3. Stop criteria
4. Budget guardrail
5. Team and capacity commitment
6. Reporting cadence

Act as a production reliability lead.

From the pilot charter, the governance framework, the
architecture audit and the operating model, produce a
production gating checklist across five dimensions:

1. Performance
2. Security and governance
3. Operational readiness
4. Adoption readiness
5. Financial controls

For each dimension: the exact pass criteria and the artifact
that proves them.

Act as a site reliability engineer.

From the architecture, the workflow and the governance
framework, produce a rollback plan:

1. The catalogue of plausible failure modes
2. The exact trigger thresholds that activate the rollback
3. The withdrawal sequence: step by step, who does what
4. The communication plan: who to inform, in what order,
   with what message

Act as a product adoption analyst.

From the target-user definitions, the usage telemetry and
the engagement survey data, produce an adoption dashboard:

1. The usage signal: who uses what, how often
2. The drop-off cohorts: who stopped using it, and when
3. The behaviour-change index: is the work being done
   differently, or is the AI one more step
4. The intervention candidates: where to act first

Act as a rigorous financial controller.

From the baseline metrics, the current metrics, the original
business case and the context on confounding factors, produce:

1. The hard savings achieved, with the math
2. The soft gains achieved, separated and labelled as such
3. The attribution confidence: for each metric, the degree of
   certainty that AI caused it, with the reasoning
4. The gap analysis: projection versus outcome, no sugar-coating

Act as a senior MLOps engineer.

From the model specifications, the input data profiles over
time, the performance metrics and the workflow change log,
produce a retraining cadence plan:

1. The drift detection signals and their thresholds
2. The retraining budget: frequency and cost
3. The model version control and rollback plan
4. The accountability: who is responsible for making sure
   retraining actually happens