What problem does it solve? Development phases accumulate invisible waste — rework, repeated gate runs, subagents that cost more than they saved, and stale rules nobody deletes. This Skill audits how a stretch of work was actually carried out, using the session transcript as evidence, and turns each finding into a concrete rule change before the context is compacted away. ## Core Features & Use Cases - Six-question audit: Counts rework, repeated gate runs, subagent cost versus payoff, sequencing mistakes, redundant re-reading, and rules made obsolete by the phase. - Evidence-based answers: Requires numbers from the transcript rather than impressions, with none as an explicit valid answer per question. - Rule lifecycle management: Lands each lesson as a diff to the relevant skill or flow document, displaces an existing rule when budgets force it, and records removals in the commit's Retro: line. - Use Case: At the end of a development phase, run the retrospective to discover that a gate was re-run eight times where two would do, then encode that as a rule so the next phase avoids it. ## Quick Start Ask the assistant to run the retrospective gate on this session's transcript and report the six answers with counts before the context is compacted.
