engineering-retrolisted

# Engineering retro Use this skill only for an explicit retrospective on completed or substantially completed work. It does not change the delivery workflow for active work. ## Scope the evidence window Start from the requested window: recent work, one release, a release range, or another bounded set of completed engineering work. Do not force the retro to revolve around one issue when the evidence spans several changes. Use existing evidence only. Prefer, in order: 1. retained Agent Bridge conversation turns for owner requests, corrections, questions, reminders, and completion reports; 2. GitHub issues, pull requests, reviews, commits, and release history for what changed and where repair loops occurred; 3. CI and qualification evidence for avoidable failures, reruns, and gaps between local and hosted checks; 4. current repository instructions, Skills, code structure, and tooling only after a friction point has been identified, to determine whether the correct behavior was already owned somewhere. Do not add telemetry, scoring infrastructure, or a new audit trail just to run the retro. ## Find intervention that matters Separate necessary owner intervention from avoidable coordination. Necessary intervention includes product decisions, new authority, genuinely ambiguous business intent, irreversible/high-cost actions, and decisions outside previously agreed scope. Avoidable intervention includes reminders to finish already-authorized work, pointing an agent at imple