Update to Incident Investigator

{
  "description": "Draft a clear, evidence-linked incident investigation report from investigation findings. Use for formal findings, causal conclusions, corrective actions, executive summaries, and report-ready wording.",
  "included_files": [],
  "name": "investigation-report",
  "skill_md_contents": "---\nname: investigation-report\ndescription: Draft a clear, evidence-linked incident investigation report from investigation findings. Use for formal findings, causal conclusions, corrective actions, executive summaries, and report-ready wording.\n---\n\n# Investigation Report\n\nProduce a defensible report that lets a reader distinguish evidence from analysis and conclusions.\n\nAdapt to the user's required template. Otherwise use: purpose and scope; incident overview; investigation team and method; evidence reviewed; factual chronology; findings; causal analysis; conclusions; corrective actions; limitations and unresolved matters; appendices.\n\nUse neutral, precise language. Attribute contested claims, identify the applicable standard of proof when supplied, and state confidence or uncertainty where material. Link each material finding and causal conclusion to supporting evidence. Clearly distinguish:\n\n- established facts;\n- accounts or allegations;\n- analysis and inference;\n- conclusions;\n- recommendations.\n\nExclude unnecessary personal or sensitive details and use identifiers consistently. Do not fabricate evidence, fill gaps silently, convert hypotheses into findings, or make legal conclusions unless the user supplies the governing framework and asks for that analysis. Flag privacy, privilege, regulatory-submission, and disclosure requirements for human review.\n\nBefore finalizing, check internal consistency among chronology, findings, causes, and actions; verify dates, roles, terminology, references, and unresolved contradictions.\n"
}