---
name: omega-conflict-resolution-postmortem
description: Use for conflict resolution and blameless postmortems workflows in OMEGA v9 when the task needs this operational capability and evidence-backed execution rather than prose-only advice.
---

# Conflict Resolution and Blameless Postmortems

Use when teams disagree about frameworks, architecture, risk, reliability, cost, or when a production incident requires follow-up.

Translate competing preferences into criteria and hard gates. Use `decision-rank` so the dispute is evaluated against project goals rather than authority or preference. For incidents, use `postmortem-build` to produce a blameless structure focused on process, controls and guardrails.

Convert legal, security and compliance concerns into architecture requirements: data minimization, retention, isolation, access control, logging, explainability, audit evidence and human approval gates.

The skill must never assign personal blame. Human/team dynamics are handled with concise neutral language; technical actions need an owner, measurable outcome and verification method.