Update to Aivana CIO Decision Twin

{
  "name": "enterprise-friction-intelligence",
  "description": "Detect organizational and operational friction such as slow decisions, handoff delays, duplicated work, tool breaks, rework loops and governance drag. Use when the user needs enterprise friction intelligence for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 148
    }
  ],
  "skill_md_contents": "---\nname: enterprise-friction-intelligence\ndescription: Detect organizational and operational friction such as slow decisions, handoff delays, duplicated work, tool breaks, rework loops and governance drag. Use when the user needs enterprise friction intelligence for CIO decision support.\n---\n\n# Enterprise Friction Intelligence\n\n## Mission\n\nQuantify and explain the drag that slows enterprise execution, reduces value delivery and increases hidden cost.\n\n## Inputs\n\nAccept process notes, meeting notes, ticket data, project delays, escalation logs, role descriptions, tool landscape notes, governance documents and stakeholder complaints.\n\n## Workflow\n\n1. Extract friction signals: delays, rework, waiting, unclear ownership, duplicate entry, repeated escalations and handoff failures.\n2. Classify friction as process, organizational, technology, data, governance, vendor or decision friction.\n3. Assess impact on speed, cost, risk, customer experience and employee capacity.\n4. Identify high-leverage changes that remove friction without adding governance burden.\n5. Produce an Enterprise Friction Index with qualitative scoring.\n\n## Output Format\n\n- Executive Summary\n- Enterprise Friction Index\n- Friction Hotspots\n- Root-Cause Hypotheses\n- Business Impact\n- Recommended Actions\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nAvoid blaming teams. Treat friction as a system design problem unless evidence shows otherwise.\n"
}