retro

Log project observations, failures, and successes into structured JSONL files.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill retro-ambrovia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/retro
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill retro-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of institutional amnesia in software development by systematically recording successes, frictions, and failures at the end of every work package.

Core Features & Use Cases

  • Structured Observation: Logs specific project outcomes into per-work-package JSONL files to avoid merge conflicts.
  • Compound Learning: Feeds data into the pipeline's compounding engine to identify recurring patterns and process bottlenecks.
  • Use Case: After completing a complex backend refactor, use this skill to document specific technical hurdles encountered during testing, ensuring the team avoids the same pitfalls in the next sprint.

Quick Start

Run the retro skill for the current work package to log observations and identify potential process improvements.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I document project post-mortems to prevent recurring errors?

Run a retro on the current work package to log observations and identify potential process improvements. It systematically records successes, frictions, and failures by applying to all pipeline phases to track technical debt and workflow friction.

What is the best way to track technical debt and workflow friction across pipeline phases?

Track technical debt and workflow friction by logging project observations into structured JSONL files. This feeds data into the pipeline's compounding engine to identify recurring patterns and process bottlenecks across all pipeline phases.

Do I need version control history and pipeline logs to generate actionable post-mortem data?

Yes, generating actionable post-mortem data requires access to version control history, pipeline logs, and work package artifacts. These inputs allow the skill to accurately track technical debt, workflow friction, and team performance metrics.

How does structured observation logging avoid merge conflicts for project retrospectives?

Structured observation logging avoids merge conflicts by writing project outcomes into per-work-package JSONL files. This isolates retrospective entries, allowing parallel documentation of successes and frictions without overwriting shared team files.

When should I use structured JSONL files for continuous process improvement?

Use structured JSONL files for continuous process improvement at the end of every work package. This timing systematically records technical hurdles and institutional knowledge, feeding data into the pipeline to prevent recurring errors.