retrospective

Name: retrospective
Availability: InStock
Author: brucebanner010198-commits

Generate structured retrospective minutes and feed results into LESSONS.md.

Updated Apr 21, 2026

Search Tags:#retrospective #governance #meetings #lessons #cadence #project-close

Ready to run

npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill retrospective-brucebanner010198-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/retrospective
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill retrospective-brucebanner010198-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retrospective skill provides a structured, repeatable process to capture lessons learned after a project close or quarterly review, ensuring outputs are stored in _meetings and fed into LESSONS.md.

Core Features & Use Cases

Defines the retro format, the mandatory attendance list, and the evidence-gathering steps.
Outputs the minutes file _meetings/<slug>-retro-<date>.md and supports multiple retro kinds (project-close, portfolio, incident, wave) as per cadence.
Supports triggers like "run the retro" or "/devsecops-agency:retro" and is used for post-close, portfolio, incident, and wave retros.

Quick Start

Invoke the retro with the phrase '/devsecops-agency:retro' after project close to generate the minutes.

Frequently Asked Questions about retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate post-project retrospective minutes and feed lessons learned into documentation?▼

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.

What types of retrospectives can I run for project governance and cadence reviews?▼

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.

How do I trigger a retrospective workflow after a project close?▼

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.

Do I need mandatory attendance and evidence gathering for a portfolio review retrospective?▼

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.

What is the best way to capture lessons learned and store retrospective outputs?▼

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.

Can I run an incident retrospective and still get standardized minutes output?▼

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.