What problem does it solve? Teams often end Sprints without inspecting how they worked, so the same process friction repeats Sprint after Sprint. This Skill runs a structured, blameless Sprint Retrospective that converts frustrations and patterns into concrete improvement actions with owners and dates, and persists systemic lessons in the project's lessons-learned memory. ## Core Features & Use Cases - Structured Retrospective Format: Guides the team through Start/Stop/Continue (or the equivalent good/improve/actions variant) across five activities, from reviewing prior actions to deciding new ones. - Actionable Improvement Actions: Enforces that every action has a description, named owner, target date, success signal, and status, limited to 1-3 actions per retro. - Lessons-Learned Bridge: Registers systemic patterns as RST files in docs/source/gestion/pm/docs/lecciones-aprendidas/ using the project's retrieval convention. - Use Case: After a Sprint where items were committed without a Definition of Ready, run the retrospective to surface the root cause, assign an action ("add DoR check to refinement") to a named owner, and record the lesson so future Sprints retrieve it. ## Quick Start Run the scrum-retrospective skill to facilitate our Sprint Retrospective and produce improvement actions with owners and dates.
