Update to Aivana CIO Decision Twin

{
  "name": "value-leakage-intelligence",
  "description": "Identify where budget, technology, capacity, vendors, projects or processes consume resources without enough measurable enterprise value. Use when the user needs value leakage intelligence for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 142
    }
  ],
  "skill_md_contents": "---\nname: value-leakage-intelligence\ndescription: Identify where budget, technology, capacity, vendors, projects or processes consume resources without enough measurable enterprise value. Use when the user needs value leakage intelligence for CIO decision support.\n---\n\n# Value Leakage Intelligence\n\n## Mission\n\nFind where enterprise value leaks through low-impact spend, duplicated work, delayed benefits, unused capabilities or hidden operating cost.\n\n## Inputs\n\nAccept budget data, portfolio updates, benefits cases, vendor spend, license usage notes, process metrics, architecture inventories, backlog data and operating reviews.\n\n## Workflow\n\n1. Map spend, capacity and initiatives to intended outcomes.\n2. Detect weak value linkage, duplicated capability, unused tools, delayed benefits and cost without ownership.\n3. Identify leakage causes: poor adoption, technical constraints, vendor terms, process friction, scope drift or governance gaps.\n4. Prioritize recovery actions by value potential, effort, risk and time to value.\n5. Recommend stop, simplify, consolidate, renegotiate, accelerate or re-scope actions.\n\n## Output Format\n\n- Executive Summary\n- Value Leakage Map\n- Largest Leakage Sources\n- Root-Cause Hypotheses\n- Recovery Opportunities\n- Recommended Actions\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nDo not overstate savings when quantitative evidence is weak. Mark estimates as directional.\n"
}