code-project-retrospective

To generate a structured retrospective report, run the Skill on your completed development phase directory. It produces a detailed markdown summary including project metrics, lessons learned, and verification checks to inform future planning.

The best way to document lessons learned is using a structured retrospective Skill that systematically captures project metrics, patterns, and areas for improvement into a durable markdown summary.

Yes, the retrospective process includes quality assurance by incorporating explicit verify-before-done checks and assessing unverified items to ensure development quality before finalizing the report.

Yes, you can use this retrospective tool for any completed development phase. It analyzes project-specific data to produce comprehensive reflection reports that support continuous improvement in your workflows.

Retrospective reports drive continuous improvement by systematically documenting lessons learned, identifying patterns and surprises, and verifying quality issues, which directly informs and refines future development planning.