Update to Aivana CIO Decision Twin

{
  "name": "crisis-command-mode",
  "description": "Convert incidents, outages, security events, compliance escalations or executive crises into a command structure, situation report, decisions, communications and action plan. Use when the user needs crisis command mode for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 135
    }
  ],
  "skill_md_contents": "---\nname: crisis-command-mode\ndescription: Convert incidents, outages, security events, compliance escalations or executive crises into a command structure, situation report, decisions, communications and action plan. Use when the user needs crisis command mode for CIO decision support.\n---\n\n# Crisis Command Mode\n\n## Mission\n\nApply the [shared decision contract](../autonomous-cio-orchestrator/references/decision-contract.md)\nfor evidence handoffs, scoring limits, and a concise first page. Do not delay urgent\ncontainment advice to complete optional scorecards; distinguish drafts from executed actions.\n\nCreate order in high-pressure enterprise situations by building a concise crisis command view for executives and responders.\n\n## Inputs\n\nAccept incident reports, outage notes, stakeholder escalations, operational updates, security findings, customer impact notes, timelines, known unknowns and draft communications.\n\n## Workflow\n\n1. Establish current situation, impact, timeline, known facts and unknowns.\n2. Identify command roles: incident lead, executive sponsor, technical lead, communications owner, customer owner, risk/compliance owner.\n3. Separate immediate containment, diagnosis, recovery, communications and prevention work.\n4. Identify executive decisions, escalation thresholds and communication needs.\n5. Produce an action plan for the next 1h, 4h, 24h and 7d.\n\n## Output Format\n\n- Executive Summary\n- Current Situation\n- Impact and Severity\n- Known Facts / Unknowns\n- Command Structure\n- Decisions Needed\n- Stakeholder Communications\n- Action Plan: 1h / 4h / 24h / 7d\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not claim incident containment or notification execution. Prepare command guidance and drafts only.\n"
}