Update to Aivana CIO Decision Twin

{
  "name": "decision-scenario-intelligence",
  "description": "Frame decisions, compare options and run qualitative or semiquantitative what-if scenarios for budgets, resources, organization, process, capacity, risk and technology changes. Use when the user needs decision scenario intelligence for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 146
    }
  ],
  "skill_md_contents": "---\nname: decision-scenario-intelligence\ndescription: Frame decisions, compare options and run qualitative or semiquantitative what-if scenarios for budgets, resources, organization, process, capacity, risk and technology changes. Use when the user needs decision scenario intelligence for CIO decision support.\n---\n\n# Decision Scenario Intelligence\n\n## Mission\n\nTurn ambiguous executive choices into structured options, scenarios, trade-offs, sensitivities and recommended decision paths.\n\n## Inputs\n\nAccept decision questions, options, constraints, risk appetite, budget or capacity assumptions, project context, process context, architecture notes, risk data and stakeholder concerns.\n\n## Workflow\n\n1. Clarify the decision, default option, alternatives, constraints and success criteria.\n2. Identify affected domains: strategy, finance, operations, security, compliance, architecture, organization and delivery.\n3. Use the risk chain as the scenario backbone.\n4. Build scenarios such as approve now, defer, approve with conditions, stop/pause, expected case, downside case and shock case.\n5. Compare options by impact, cost, risk, timing, dependencies, reversibility and confidence.\n6. Run sensitivity reasoning for major assumptions.\n7. Add commitment integrity checks: date, scope, budget, capacity, controls, owner, recovery path and reversibility.\n8. Add kill criteria for each option.\n9. Recommend a decision path, safeguards, trigger points and next actions.\n\n## Option Contract\n\nApply the [shared decision contract](../autonomous-cio-orchestrator/references/decision-contract.md),\nincluding stable claim/option IDs, the numeric scoring gate, and upstream abstention.\n\nEvery option should show:\n\n- value upside\n- risk accepted\n- evidence needed\n- owner and approval gate\n- reversibility\n- board narrative risk\n- decision SLA\n- kill criteria\n\n## Output Format\n\n- Executive Summary\n- Decision Frame\n- Options Compared\n- Scenario Matrix\n- Impact / Risk / Cost View\n- Commitment Integrity Score\n- Sensitivities\n- Recommended Decision\n- Safeguards and Triggers\n- Scenario Kill-Switch\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nUse qualitative or directional scoring unless reliable numeric inputs are provided. Make uncertainty visible.\n"
}