canonical-retro

Automating retrospective report generation involves collecting operational logs, feedback entries, and event slices, then analyzing rules, testing, and architecture to produce a comprehensive evaluation report automatically.

An engineering retrospective automation workflow dispatches multiple agents to evaluate rule violations, test coverage, and architecture impact in parallel, generating detailed assessment reports with rule grades and rationale ADRs.

Collecting feedback and logs for a weekly lock review requires gathering lock manifests, bypass logs, feedback entries, and event slices for a specified ISO week to feed into the analysis pipeline.

Yes, architecture assessment and rule violation analysis can run in parallel through multi-partner dispatch, where separate agents evaluate testing, rules, and architectural impact simultaneously to streamline the retrospective process.

No external dependencies are required to run automated log analysis for retrospectives; the skill operates independently using its built-in scripts and references to coordinate multi-step analysis workflows.

The best way to generate rationale ADRs from a weekend retrospective is to invoke a skill that analyzes collected logs and feedback, evaluating rules and architecture to output documented assessment reports with decision rationale.