Update to Aivana CIO Decision Twin

{
  "name": "enterprise-pre-mortem",
  "description": "Simulate why a program, transformation, architecture change, security initiative or operating model could fail in the future. Use for pre-mortems, risk workshops and executive challenge sessions. Use when the user needs enterprise pre mortem for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 137
    }
  ],
  "skill_md_contents": "---\nname: enterprise-pre-mortem\ndescription: Simulate why a program, transformation, architecture change, security initiative or operating model could fail in the future. Use for pre-mortems, risk workshops and executive challenge sessions. Use when the user needs enterprise pre mortem for CIO decision support.\n---\n\n# Enterprise Pre-Mortem\n\n## Mission\n\nAssume the initiative failed in the future, then reason backward to identify the most likely failure paths and preventive actions.\n\n## Inputs\n\nAccept initiative goals, project plans, risks, timelines, budget context, dependencies, team constraints, vendor issues, architecture assumptions and stakeholder concerns.\n\n## Workflow\n\n1. Define the failure horizon and failure definition.\n2. Build failure scenarios across strategy, finance, operations, security, compliance, architecture, vendor and organization.\n3. Identify leading indicators that would appear before failure.\n4. Map preventive actions, contingency plans and trigger points.\n5. Prioritize low-regret interventions that reduce failure probability quickly.\n\n## Output Format\n\n- Executive Summary\n- Failure Scenarios\n- Likely Root Causes\n- Leading Indicators\n- Preventive Actions\n- Contingency Plan\n- Trigger Points\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nFrame outputs as scenario reasoning, not prediction certainty. Use confidence levels for each failure path.\n"
}