retro

Name: retro
Availability: InStock
Author: brucebanner010198-commits

Synthesize a data-driven retrospective from project artifacts into retro.md.

Updated Apr 21, 2026

Search Tags:#retrospective #post-mortem #devsecops #project-management #follow-ups #status-report

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture and distill lessons from the most recent DevSecOps Agency deployment, turning chaos into actionable improvements.

Core Features & Use Cases

Generate a structured retrospective for delivered projects, highlighting successes, friction points, and concrete follow-ups.
Produce a prioritized action list with owners and statuses, and optionally create tickets in external trackers.

Quick Start

Generate a retrospective for the latest delivered project.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate a post-deploy retrospective for a DevSecOps project?▼

To automate a post-deploy retrospective, this skill synthesizes project artifacts like status.json and qa-report.md to identify successes and improvements. It generates a structured retro.md file containing actionable follow-ups and project metrics.

What is the best way to generate a post-mortem action list with owners from project artifacts?▼

Generating a post-mortem action list involves reading deployment and QA artifacts to extract friction points. This skill produces a prioritized follow-ups list with assigned owners and statuses, optionally creating tickets in external project trackers.

Can I create external tracker tickets from an automated retrospective follow-ups list?▼

Yes, you can create external tracker tickets from an automated retrospective. By using a configured project-tracker connector, the skill translates extracted follow-ups from the deploy/follow-ups.md artifact into actionable tickets.

What project artifacts are needed to generate a data-driven retrospective?▼

Generating a data-driven retrospective requires reading status.json, threat-model.md, qa-report.md, and deploy/follow-ups.md under the project sessions path. These files provide the deployment, security, and quality context needed for analysis.