What problem does it solve? Teams often end Sprints without inspecting how they worked, so the same process friction, impediments, and failures repeat Sprint after Sprint. This Skill runs the Scrum Sprint Retrospective ceremony in a blameless format and converts discussion into concrete, owned improvement actions plus durable lessons-learned records. ## Core Features & Use Cases - Structured Retrospective Format: Guides the team through Start/Stop/Continue (or the equivalent what-went-well / what-to-improve / actions variant) with five defined activities, from reviewing prior actions to deciding new ones. - Actionable Improvement Commitments: Enforces that every action has a description, named owner, target date, success signal, and status, limited to 1-3 actions per retro. - Lessons-Learned Memory Bridge: Registers systemic patterns as RST lesson files in the project's lessons-learned directory so they survive the Sprint and are retrievable in future sessions. - Use Case: After a Sprint where items were committed without a Definition of Ready, run the retrospective to surface the root cause, commit an action like "add DoR verification to refinement" with an owner and date, and record the pattern as a project lesson. ## Quick Start Run the scrum retrospective for the Sprint that just ended and produce improvement actions with owners and dates.
