agentleFS
peterbamuhigirepeterbamuhigire/business-plan-skills/skills/meta-strategy/meta-digital-transformation/SKILL.md

meta-digital-transformation

Skill4 starsChanged 18 days agoMITView on GitHub

Use when the client wants a digitally enabled growth strategy, operating model, or business-model redesign. Use the relevant plan-section skill for section drafting.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the client wants a digitally enabled growth strategy, operating model, or business-model redesign.

    line 20
  2. Distinctive:

    Use when technology choices affect customer acquisition, fulfilment, service quality, data, or unit economics.

    line 21
  3. Distinctive:

    Use when a plan needs to test platform, marketplace, subscription, or product-as-a-service opportunities.

    line 22
  4. Distinctive:

    Use when digitisation investments need to be prioritised by business case rather than trend.

    line 23
  5. Distinctive:

    Do not use to bolt fashionable tools onto a weak business model.

    line 27
  6. Very specific:

    Do not use when the task only needs the AI section.

    line 28
  7. Distinctive:

    Do not recommend full digital transformation when the immediate problem is basic execution discipline or absent demand evidence.

    line 29
  8. Distinctive:

    Test whether the right move is workflow digitisation, platform participation, platform creation, subscription/access model, or simple …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- dual-compat-start -->

Digital Transformation Meta-Skill

Overview

Use this meta-skill when a business plan or strategy needs a serious answer to the question: how should this business digitise and use technology in a way that is commercially justified, context-fit, and operationally realistic. It sits above 14-ai-integration and helps ensure that AI recommendations live inside a broader digital strategy rather than replacing one.

Use When

  • Use when the client wants a digitally enabled growth strategy, operating model, or business-model redesign.
  • Use when technology choices affect customer acquisition, fulfilment, service quality, data, or unit economics.
  • Use when a plan needs to test platform, marketplace, subscription, or product-as-a-service opportunities.
  • Use when digitisation investments need to be prioritised by business case rather than trend.

Do Not Use When

  • Do not use to bolt fashionable tools onto a weak business model.
  • Do not use when the task only needs the AI section; use 14-ai-integration for that narrower purpose.
  • Do not recommend full digital transformation when the immediate problem is basic execution discipline or absent demand evidence.

Required Inputs

InputSource / providerRequired?If absent
Digital Transformation brief and decision audienceClient, plan owner, or approved project filesYesStop before making a recommendation; state the missing decision context.
Claims, assumptions, and supporting evidenceSource register, model, research notes, interviews, or operating recordsYesSeparate known facts from assumptions and return a qualified gap list.
Authority and delivery constraintsRequesting owner and repository instructionsYesRemain read-only and produce a draft or review only.
  • Current business model, offer, target customers, and growth objective
  • Existing workflows, systems, channels, data, and digital tools
  • Commercial pain points: acquisition, conversion, fulfilment, retention, leakage, reporting, or coordination
  • Capacity, budget, team capability, and adoption constraints
  • Country, infrastructure, and regulatory realities

Workflow

  1. Diagnose the current business model, customer journey, and operating bottlenecks.
  2. Assess digital maturity across customers, competition, data, innovation, and value.
  3. Identify digitisation opportunities across channel, process, data, service, and business-model layers.
  4. Test whether the right move is workflow digitisation, platform participation, platform creation, subscription/access model, or simple systems discipline.
  5. Prioritise options using practical business-case logic: value created, cost, risk, adoption burden, and time to benefit.
  6. For software, SaaS, platform, or cloud-dependent businesses, assess DevOps maturity: release path, pipeline discipline, observability, incident response, security checks, backup/restore, and cloud cost control.
  7. Produce a phased roadmap with owners, KPIs, dependencies, and handoffs to 14-ai-integration, 10-financial-projections, 11-funding-request, and 13-implementation-timeline as needed.

Decision, stop, and recovery controls

  • Decision point: confirm that the requested output is the staged digital-transformation roadmap and that the decision concerns which capability to digitise first and what to defer.
  • Stop condition: halt the affected conclusion if required evidence is missing (customer problem, process baseline, data readiness, and investment case) or if the work could lead to this identified risk: funding technology that has no customer or operating mechanism.
  • Recovery: obtain the missing record or reviewer, repeat the affected check, and update the exception record before release.

Quality Bar

  • Recommendations solve real customer or operating problems rather than decorating the plan with tech language.
  • Digital choices fit the business stage, market context, and team capability.
  • Data, channel, and process implications are explicit.
  • Major technology bets have option logic, cost logic, and staged rollout discipline.
  • Software and platform recommendations include operating capability, not just build features: delivery process, monitoring, support, incident learning, and security ownership.

Anti-Patterns

  • Equating digitisation with launching a website or buying software.
  • Recommending AI before fixing process, data, or ownership.
  • Assuming platform economics where network effects are absent.
  • Treating digital transformation as capex with no adoption, governance, or KPI logic.
  • Treating a generic digital transformation template as a conclusion. Correction: tie each choice to the named audience, evidence, and operating constraint.
  • Applying the wrong neighbouring route to meta digital transformation. Correction: confirm the decision and route to the named neighbour before analysis.
  • Treating an assumption as verified evidence. Correction: label it, cite its source or owner, and assign a verification action.
  • Recommending action without a decision threshold. Correction: state the measurable acceptance condition and review trigger.
  • Recording an unavailable check as passed. Correction: mark it not assessed and state the consequence for the decision.
  • Mutating or publishing during an analysis-only task. Correction: remain read-only until the owner gives explicit authority.

Outputs

ArtefactConsumerObservable acceptance condition
Digital Transformation deliverableNamed decision-maker or plan authorThe recommended choice, assumptions, countercase, and next action are explicit.
Evidence and exception registerReviewer, funder, board, or implementation ownerEvery load-bearing claim is sourced or labelled as an assumption; missing checks are not shown as passes.
  • Digital maturity and opportunity diagnosis
  • Prioritised digitisation and business-model options
  • Business-case-tested roadmap for technology investment
  • Cross-references for execution, finance, funding, and AI follow-on work

References

  • references/business-agility-readiness-map.md - B18-A01 people, process, tools, evidence, reversible slice, and rollback readiness contract.
  • references/digital-business-model-redesign-tests.md (Test 1) - five-domain strategy lens: customers, competition, data, innovation, value
  • references/digital-business-model-redesign-tests.md (Test 2) - demand-driven redesign, outside-in thinking, value networks, platform logic, and product-as-a-service options
  • references/digital-business-model-redesign-tests.md (Test 3) - digital transaction models, revenue logic, and supply-side/collaborative digitisation
  • ../meta-critical-thinking-business-logic/references/business-case-test.md - options, do-nothing case, incremental economics, and sensitivity logic for major digital investments
  • ../../pipeline/08-operations-plan/references/digital-delivery-operating-model.md - DevOps, CI/CD, release, observability, incident response, PHP/LAMP, cloud-native, and digital service reliability patterns for technology businesses
  • ../14-ai-integration/SKILL.md - use after the broader digital strategy is clear and the AI layer must be specified

Evidence Produced

EvidenceFormatAcceptance condition
Staged digital-transformation roadmap decision traceSources, calculations, assumptions, countercase, and selected actionA reviewer can trace the selected action and rejected alternatives to the cited inputs.
Exception recordFailed and not-assessed checks with owner and due actionThe register exposes every unresolved exception that could lead to funding technology that has no customer or operating mechanism.

Capability and Permission Boundaries

Read supplied records and use non-mutating checks to produce the staged digital-transformation roadmap; drafting the authorised roadmap without buying or deploying systems is permitted when requested. Do not publish, contact third parties, alter live systems, commit funds, or claim legal, tax, audit, valuation, ESG, or investment assurance without the owner's explicit authorisation and the appropriate reviewer.

Degraded Mode

If customer problem, process baseline, data readiness, and investment case cannot be obtained, return a qualified staged digital-transformation roadmap covering only the checks that remain supportable. Leave this decision unresolved: which capability to digitise first and what to defer. Record the evidence owner and next check; an inaccessible source, tool, or reviewer is never a pass.

Decision Rules

Decision conditionActionFailure or risk avoided
Evidence is sufficient to decide: which capability to digitise first and what to deferRecord the conclusion, source trail, owner, and review trigger in the staged digital-transformation roadmap.Risk of funding technology that has no customer or operating mechanism
Material evidence conflicts or remains uncertainCompare the first-stage capability against the current manual process on customer outcome, control burden, adoption, and payback before sequencing it.Selecting an option without resolving the decision-relevant uncertainty
Required evidence is missing: customer problem, process baseline, data readiness, and investment caseMark the decision on which capability to digitise first and what to defer not assessed in the staged digital-transformation roadmap, and send it to the process owner and investment sponsor.Otherwise, the work risks funding technology that has no customer or operating mechanism

Quality Standards

Accept the staged digital-transformation roadmap only when evidence is sufficient for this decision: which capability to digitise first and what to defer. Assumptions and countercases remain visible, calculations and cross-references reconcile, and the reviewer can see how the recommendation addresses the risk of funding technology that has no customer or operating mechanism.

Worked Example

A distributor requests an AI platform while orders still arrive through unstructured messages. Sequence order capture and clean product data first; approve later automation only after adoption and error-rate evidence.

<!-- dual-compat-end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.