Synthesize sprint notes and artifacts into a project retrospective document.
npx skills add https://github.com/zabuuq/sdd-plugin --skill retro-zabuuq
Please help me install this Agent Skill. Skill: retro Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/retro Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill retro-zabuuq
It prevents valuable delivery learnings from getting lost by turning scattered sprint outcomes, process notes, and open concerns into a single, project-level retrospective document.
Run /sdd:retro after completing at least one planning or sprint cycle so the plugin can read your process notes and generate docs/retro.md.
High-intent search queries and answers about installing and using this skill.
A project-wide retrospective synthesizes sprint process notes, PRD artifacts, and open concerns into a single document. It runs a structured interview to assess planning quality, sprint cadence, friction, communication, and final product-versus-intent outcomes.
The best way to document product-versus-intent outcomes is through a structured retrospective that compares final delivery against the original PRD scope. This captures scope changes, quality metrics, and technical debt while resolving logged open concerns.
To close out open concerns and update project state, the Skill resolves or carries forward items in docs/open-concerns.md and writes final outputs to docs/retro.md and docs/project-state.json. This ensures workflow closure after your sprint cycles.
You should not run a project retrospective without completing at least one planning or sprint cycle. The Skill requires loading shared guide behavior and reading existing process notes to synthesize outcomes and generate the final retro document.
A guided retrospective interview improves workflow by structuring user reflection one question at a time across planning quality, sprint cadence, friction, and communication patterns. It summarizes logged plugin feedback to turn insights into actionable planning inputs.
You need PRD or spec artifacts to perform a comprehensive sprint review and retrospective because the Skill assesses final product-versus-intent by comparing outcomes against the original scope. These artifacts drive the structured interview and document generation.
SebastienDegodezReview DISCOVER artifacts for completeness and prioritization quality.
jesseotremblayIdentify and classify industry trends with lifecycle staging and impact assessment.
zabuuqRecord sprint feedback notes to docs/sdd-feedback.md for the SDD plugin.
rhuangabrielsantosReview PRD implementation code and generate structured issue files.
