documentation-updates

Capture lessons learned by running a structured postmortem workflow that summarizes what happened, what went well, and what didn't, then writing those insights into project documentation like AGENTS.md or CLAUDE.md to prevent recurring mistakes.

A structured postmortem reflection summarizes project events, identifies what went well and what failed, and creates a standardized record of pitfalls, best practices, and patterns to drive process improvement and prevent repeat mistakes.

To keep AGENTS.md and CLAUDE.md files fresh, update them after significant work or feedback by appending concise postmortem reflections, pitfalls, and best practices that reflect the latest project insights.

Yes, the postmortem workflow is applicable across projects and contexts, allowing you to update both per-project documentation and global references to maintain consistent knowledge-management practices everywhere.

Update per-project docs like AGENTS.md or CLAUDE.md with context-specific pitfalls, and update global documentation when significant work or feedback reveals broad insights, best practices, or patterns relevant to future work across all projects.