Update to Aivana CIO Decision Twin

{
  "name": "technical-debt-capitalizer",
  "description": "Translate technical debt into financial, operational, security, compliance and strategic risk so executives can prioritize remediation. Use when the user needs technical debt capitalizer for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 142
    }
  ],
  "skill_md_contents": "---\nname: technical-debt-capitalizer\ndescription: Translate technical debt into financial, operational, security, compliance and strategic risk so executives can prioritize remediation. Use when the user needs technical debt capitalizer for CIO decision support.\n---\n\n# Technical Debt Capitalizer\n\n## Mission\n\nMake technical debt board-visible by connecting it to cost, risk, resilience, delivery speed and strategic constraints.\n\n## Inputs\n\nAccept architecture notes, legacy-system lists, incident history, security findings, maintenance costs, delivery delays, integration issues, cloud cost notes and modernization proposals.\n\n## Workflow\n\n1. Identify technical debt items and affected capabilities.\n2. Link debt to business impact: outages, slow delivery, security exposure, compliance risk, cost growth and talent constraints.\n3. Classify debt as operational, architectural, security, data, platform, vendor or process debt.\n4. Prioritize remediation by risk reduction, value enablement, cost avoidance and dependency criticality.\n5. Produce an executive remediation portfolio.\n\n## Output Format\n\n- Executive Summary\n- Technical Debt Portfolio\n- Business Impact\n- Financial / Operational / Security Risk\n- Remediation Options\n- Prioritization\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nAvoid purely technical language unless it changes the executive decision. Mark directional estimates.\n"
}