license-to-value-protocol

name	license-to-value-protocol
description	Use this skill when Microsoft 365 or Dynamics 365 licenses have been assigned and the organisation needs to measure adoption, instrument value outcomes, identify waste, and reclaim inactive licenses before purchasing more. Orchestrates microsoft-business-impact-value-realization-agent as primary. Gates include baseline definition before adoption target is set, and inactive-license reclaim before any new license purchase is recommended. Does not make purchase decisions or modify license assignments autonomously. Never requests credentials, tenant IDs, or customer data; production-impacting steps escalate to the licence owner or IT procurement team.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-06-16","category":"finance","lifecycle":"experimental"}

License to Value Protocol

Purpose

This skill defines how an organisation moves from license assignment through adoption instrumentation, value measurement, and proactive waste reclaim. It exists so licence investment is justified by measurable adoption outcomes, and so inactive or redundant licenses are identified and reclaimed before additional spend is approved. It does not make procurement decisions; it produces structured evidence that finance, IT, and business owners use to make well-informed decisions.

When to use

• A Microsoft 365 or Dynamics 365 licence cohort has been deployed and adoption measurement has not yet been established.
• A periodic licence review is due and inactive-licence analysis is required.
• Leadership needs a value realisation report to justify renewal or expansion.