retro

Aggregate feature plans, reports, and audits into a condensed retrospective markdown file.

4|Updated Mar 23, 2025

Search Tags:#planning #patterns #retrospective #feature #lessons #risks #retro

Ready to run

npx skills add https://github.com/matochu/pythia --skill retro-matochu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/matochu/pythia/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/matochu/pythia --skill retro-matochu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams synthesize a feature-level retrospective by consolidating patterns, risks, and lessons from all plans and reports in the feature, producing a single, actionable retro file.

Core Features & Use Cases

Aggregates artifacts from plans, implementation reports, reviews, and audits to surface recurring themes.
Distills patterns, risks, and lessons into actionable recommendations for future plans.
Outputs the retrospective to {feature-dir}/notes/{feature-slug}.retro.md for easy reference and archival.

Quick Start

Invoke the retro skill with the feature identifier to generate a retrospective for that feature.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a feature retrospective from multiple plans and reports?▼

A feature retrospective synthesizes patterns, risks, and lessons from multiple plans, implementation reports, reviews, and audits into a single, actionable file for easy reference and archival.

What is the best way to consolidate feature lessons and risks for future planning?▼

The best way to consolidate feature lessons and risks is to distill recurring themes from all feature artifacts, producing actionable recommendations that can be directly applied to future plans.

How do I aggregate feature artifacts into a single retrospective file?▼

Aggregate feature artifacts by invoking the synthesis process on the feature identifier, which outputs the retrospective to notes/{feature-slug}.retro.md for easy reference and archival.

Do I need any external dependencies to synthesize feature plans and audits?▼

No external dependencies are required to synthesize feature plans and audits into a retrospective; the process operates entirely on the artifacts within the feature directory.

Does generating a retrospective overwrite existing feature notes?▼

Generating a retrospective overwrites any existing file in the feature notes path, replacing the previous notes/{feature-slug}.retro.md with the newly synthesized output.