Retrospective Protocol

Name: Retrospective Protocol
Availability: InStock
Author: PDLC-OS

Analyze completed feature cycles to generate structured retrospectives with per-agent contributions and learnings.

Updated Aug 27, 2026

Search Tags:#learning #retrospective #agile #memory #episode #reflect #pdlc

Ready to run

npx skills add https://github.com/pdlc-os/pdlc --skill retrospective-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Retrospective Protocol
Source: https://github.com/pdlc-os/pdlc/tree/main/skills/reflect
Command: npx skills add https://github.com/pdlc-os/pdlc --skill retrospective-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Retrospective Protocol provides a structured, auditable way to capture contributions, outcomes, and learning from a feature cycle, ensuring accountability and continuous improvement.

Core Features & Use Cases

Per-agent contributions documented with roles and impact.
Shipping streak, metrics snapshot, guardrail analysis compiled into a cohesive retrospective.
Tech debt log and actionable improvements captured for future iterations.
Used at the Reflect phase to generate an episode's "Reflect Notes" and update OVERVIEW and STATE accordingly.

Quick Start

Activate the Reflect protocol at the end of a cycle to generate and append the retrospective to the episode.

Frequently Asked Questions about Retrospective Protocol

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

FAQPage Schema

How do I generate a structured agile retrospective from completed feature cycle logs?▼

To generate an agile retrospective, analyze completed feature cycle logs including episode files, reviews, and STATE logs. This produces a structured retrospective capturing per-agent contributions, guardrails, and actionable learnings for continuous improvement.

What is a structured retrospective protocol and when do I need it?▼

A structured retrospective protocol is a process that analyzes a completed feature cycle to record contributions, outcomes, and learnings. You need it during the Reflect phase to ensure accountability and drive continuous improvement after shipping.

How to document per-agent contributions and tech debt in a PDLC Reflect phase?▼

Document per-agent contributions and tech debt by activating the Reflect protocol at the end of a cycle. It compiles per-agent roles, impact, shipping streaks, metrics snapshots, and guardrail analysis into a cohesive retrospective with actionable improvements.

Can I use this retrospective protocol for agile cycles from inception to ship?▼

Yes, you can use this retrospective protocol for agile cycles from Inception to Ship. It applies to completed PDLC cycles, drawing inputs from episode files and STATE logs to generate actionable insights and satisfy Reflect Notes logging requirements.

What elements are required in a Reflect Notes section for an agile retrospective?▼

A Reflect Notes section for an agile retrospective requires seven specific elements. It logs per-agent contributions, shipping streaks, metrics snapshots, guardrail analysis, tech debt logs, and actionable learnings while updating OVERVIEW and STATE files accordingly.

Best way to capture episode learnings and update STATE logs after a feature ship?▼

The best way to capture episode learnings is to activate a structured retrospective protocol after shipping. It analyzes the completed cycle to generate Reflect Notes, compiling contributions and guardrails while automatically updating OVERVIEW and STATE logs.