sg-retro

Run structured GSD phase retrospectives with selectable lenses and append lessons to a dated markdown file.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-retro
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-retro
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, grep, sed, awk, ls, wc, date.

What problem does it solve?

This skill removes the fragile, manual handoff of retrospective notes by automatically collecting phase artifacts and git context, then structuring them into lens-based lessons appended to a consistent lessons file.

Core Features & Use Cases

  • Structured multi-lens retrospectives: Run one or more of six lenses (Start/Stop/Continue, 4Ls, DSPM, Sailboat, Five Whys, Conversation Analyzer) in a single invocation.
  • Automatic context gathering: Reads phase context, plans, summaries, and recent git log/diff to keep outputs grounded in what actually changed.
  • Persistent learning loop: Appends consolidated results to .planning/lessons/{NN}-{YYYY-MM-DD}.md so lessons flow forward across cycles.

Quick Start

Run sg-retro with a phase number and one or more lens codes like: sg-retro 14 ssc dspm.

Frequently Asked Questions about sg-retro

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

FAQPage Schema
How do I run a structured retrospective using git history and phase artifacts?

To run a structured retrospective, you invoke the tool with a phase number and lens codes. It automatically gathers git logs, diffs, and phase artifacts, then appends the analysis to a dated markdown lessons file.

What is the best way to automate action items and lessons learned from a project phase?

Automating action items requires applying structured lenses like Start/Stop/Continue or Five Whys to phase outputs. This tool sequences multi-lens evaluations and writes consolidated learning loops to a persistent markdown file.

Can I use the Five Whys analysis technique for my software development cycle?

Yes, Five Whys is one of the selectable lenses available for analysis. You can apply it alongside other frameworks like 4Ls or Sailboat to extract root causes and patterns from your phase context and git history.

Does this retrospective tool require specific files or directories to exist before running?

Yes, it requires existing phase context, plans, and summary artifacts. It reads these inputs along with git history to validate phase data before safely appending results to the `.planning/lessons/` directory.

How do I extract learning loops and risks from git context and phase summaries?

Extraction happens by applying multi-lens sequencing to automatically collected git context and phase artifacts. The tool grounds decisions, risks, and patterns in actual code changes before writing them to a lessons file.