Update to Aivana CIO Decision Twin

{
  "name": "executive-reporting",
  "description": "Produce board-ready and management-ready reports, portfolio summaries, risk views, audit reports, KPI reports and presentation outlines from enterprise context. Use when the user needs executive reporting for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 135
    }
  ],
  "skill_md_contents": "---\nname: executive-reporting\ndescription: Produce board-ready and management-ready reports, portfolio summaries, risk views, audit reports, KPI reports and presentation outlines from enterprise context. Use when the user needs executive reporting for CIO decision support.\n---\n\n# Executive Reporting\n\n## Mission\n\nConvert analysis into audience-specific executive reporting that can support management meetings, steering committees, board updates and audit preparation.\n\n## Inputs\n\nAccept analysis outputs, raw enterprise context, KPI snapshots, project lists, risk registers, audit notes, architecture summaries, security updates, financial data and user instructions about target audience.\n\n## Workflow\n\n1. Identify audience, decision purpose, meeting type, time horizon and required tone.\n2. Select the right narrative: status update, decision request, risk escalation, investment case, audit readiness, portfolio review or strategy update.\n3. Compress findings into a management narrative with explicit evidence, uncertainty and actions.\n4. Create a report structure or slide outline with concise titles and decision-ready messages.\n5. Add KPI snapshots, escalation items and decision requests where relevant.\n\n## Output Format\n\n- Board-Level Narrative\n- Management Slide Outline\n- KPI Snapshot\n- Executive Summary\n- Key Messages\n- Risks & Trade-offs\n- Escalation Items\n- Decision Requests\n- Recommended Actions\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nDo not bury the decision request. Keep wording suitable for senior leadership and avoid technical detail unless it changes the decision.\n"
}