retrospective

Automating a post-project retrospective requires a structured workflow that generates standardized minutes documents and feeds results into a lessons learned file. This skill enforces mandatory attendance, evidence gathering, and outputs to a meetings directory and LESSONS.md file.

Retrospectives for project governance support multiple kinds including project-close, portfolio reviews, incident analysis, and wave retrospectives. Each type follows cadence guidelines to ensure standardized output and validate the final minutes against governance requirements.

Triggering a retrospective workflow requires invoking the process with a defined command phrase like '/devsecops-agency:retro' or 'run the retro' after project close. This generates a structured minutes file named with the project slug and date in the meetings directory.

Mandatory attendance and evidence gathering are required for portfolio review retrospectives. The retrospective process enforces these governance steps to ensure standardized output and validates the final minutes against the defined cadence guidelines.

The best way to capture lessons learned is through a structured, repeatable retrospective process that outputs minutes files to a meetings directory and feeds results into LESSONS.md. This ensures outputs are stored consistently and accessible for future reference.

Incident retrospectives produce standardized minutes output validated against cadence guidelines. The workflow generates a minutes file in the meetings directory using the incident slug and date, then feeds the captured lessons into the LESSONS.md file.