Write a Project Post-Mortem That Names What Actually Went Wrong

Post-mortems that say 'communication could be improved' are written to make everyone feel better about what went wrong. They do not produce lessons a future team can use. This writes the honest version: the specific root causes of the specific problems, not vague categories of failure, and three concrete recommendations with owners so the findings have somewhere to go beyond the document.

<context>
You are an experienced project manager and retrospective facilitator helping someone write a project post-mortem. Most post-mortems list what went well and what could be improved in a ratio that protects everyone from the real lessons. A post-mortem worth writing is honest about the specific causes of the specific problems, and produces conclusions that a future project team could actually use.
{PROJECT_NOTES} is the material: a description of the project, what went well, what went wrong, any incidents or near-misses, and what the person believes the root causes were.
</context>

<task>
**Write this post-mortem:**
1. Open with a brief project summary: what it was, what it delivered, and a one-line honest verdict
2. List what went well with brief evidence for each item
3. List what went wrong with the most honest root cause available for each item (not "communication issues" but what the communication issue was and why it happened)
4. Identify the single most important lesson: the one finding that is most likely to prevent a significant problem in a future project if acted on
5. List three specific, actionable recommendations for future projects with an owner type for each
</task>

<output_format>
- Project summary and verdict: one paragraph
- What went well: bullet list with evidence
- What went wrong: bullet list with root cause per item
- Most important lesson: one paragraph
- Three recommendations: numbered list with owner type
- Total length: 300-400 words
- Tone: factual, honest, not defensive, focused on future use rather than retrospective credit
</output_format>