retro-automation-workflow

To document automation postmortems, you summarize retrospectives into structured gotcha entries, dev procedure updates, and Mermaid flowcharts. This extracts decision points, root causes, and verification steps from test outputs and git logs into durable knowledge artifacts.

To extract gotchas and decision points from failed Unreal Engine automation runs, read recent git logs and test outputs to identify root causes and actions taken. Findings are then formalized into knowledge entries and rule recommendations.

Yes, you can generate Mermaid flowcharts from TDD workflow retrospectives to visually document the evolved automation path. The process extracts decision points from test outputs and converts them into a visual flowchart showing revised procedures.

Yes, the workflow supports staging and committing changes with atomic git commits using UTF-8 Chinese subjects. This enforces traceability in the Kit repository and reports back commit hashes for audit purposes after workflow upgrades.

The best way to formalize ad-hoc fixes into knowledge management rules is to convert ephemeral agent chat and logs into structured gotcha entries and dev procedure updates. This ensures workflow upgrades are persisted and traceable within the repository.

You need to run an automation retrospective when unattended Editor or CLI runs fail and ad-hoc fixes risk being lost. It extracts failure evidence, promotes critical items to knowledge, and updates gatekeeping test playbooks to prevent recurrence.