retro

Generate a structured RETROSPECTIVE.md documenting outcomes and lessons from completed projects.

1|1|Updated Mar 19, 2026

Search Tags:#metrics #retrospective #artifacts #reflection #process-improvement #project-review #RETROSPECTIVE.md

Ready to run

npx skills add https://github.com/parandurume-labs/duru-conductor --skill retro-parandurume-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/parandurume-labs/duru-conductor/tree/main/skills/retro
Command: npx skills add https://github.com/parandurume-labs/duru-conductor --skill retro-parandurume-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standalone retrospective facilitator that helps teams reflect on completed work, capture lessons learned, and generate a structured RETROSPECTIVE.md.

Core Features & Use Cases

Independent retrospectives for software, content, or mixed projects.
Detects and uses existing artifacts (INTAKE.md, PLAN.md, BUILD-LOG.md, REVIEW.md) when available.
Guides through collecting quantitative metrics and structured reflection.
Produces RETROSPECTIVE.md with a consistent artifact header for provenance.

Quick Start

Start a retrospective by saying retro and answer the guided prompts to generate RETROSPECTIVE.md.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a structured RETROSPECTIVE.md for a completed project?▼

You generate a RETROSPECTIVE.md by starting a guided session that collects quantitative metrics and reflection inputs. It analyzes completed software, content, or mixed projects to produce a structured file.

What is a project retrospective and when do I need one?▼

A project retrospective is a structured review of completed work to capture lessons learned. You need one after finishing software, content, or mixed projects to document outcomes and drive process improvement.

How do I document lessons learned and project outcomes effectively?▼

You document lessons learned by enforcing artifact awareness and collecting quantitative metrics during a guided reflection. This generates a RETROSPECTIVE.md with a consistent header for artifact provenance.

Can I run a retrospective for solo work or does it require a collaborative team?▼

You can run a retrospective for both solo sessions and collaborative team reviews. The guided reflection process adapts to individual or group settings to document project outcomes.

Does the retrospective process require existing project artifacts like INTAKE.md?▼

The retrospective process does not require existing artifacts but detects and uses them when available. It automatically incorporates files like INTAKE.md, PLAN.md, and BUILD-LOG.md to enrich the review.

What is the best way to capture quantitative metrics during a project review?▼

The best way to capture quantitative metrics is through a guided reflection process that enforces metrics collection. This ensures your project review accurately documents measurable outcomes alongside qualitative lessons.