retro

Record lessons learned from completed work into structured retro artifacts.

6|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/rjroy/vibe-garden --skill retro-rjroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/rjroy/vibe-garden/tree/main/lore-development/skills/retro
Command: npx skills add https://github.com/rjroy/vibe-garden --skill retro-rjroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of losing valuable insights by systematically reviewing completed work and recording lessons learned.

Core Features & Use Cases

  • Post-feature retro reviews to capture what went well and what could be improved.
  • Periodic reflections to maintain organizational memory and drive continuous improvement.
  • Graduation of lessons to higher scopes within projects via structured artifacts and frontmatter.

Quick Start

Run the retro skill after finishing a feature to collect insights from related .lore/ artifacts and save a retro under .lore/retros/.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I capture lessons learned after completing a project feature?▼

To capture lessons learned, run a retrospective review after finishing a feature. The skill collects insights from related artifacts and saves a structured retro record under a dedicated directory to prevent knowledge loss.

What is the best way to organize project retrospectives for continuous improvement?▼

Organizing project retrospectives involves storing structured artifacts with clear sections and tags in a dedicated retros directory. This enforces a consistent workflow for periodic reflections and maintains organizational memory.

How does a post-feature retro review prevent knowledge loss?▼

A post-feature retro review prevents knowledge loss by systematically capturing what went well and what needs improvement. It records these insights as structured artifacts with frontmatter metadata for future reference.

Can I graduate a specific lesson learned to a higher scope across projects?▼

Yes, you can graduate lessons learned to higher scopes across projects. The retrospective workflow supports elevating insights from individual feature reviews to broader organizational contexts using structured artifacts.

Do I need a specific folder structure to save retrospective artifacts?▼

Yes, retrospective artifacts are saved under a `.lore/retros/` directory. The skill enforces this structured workflow to ensure lessons learned are consistently organized and easily retrievable.