gds-retrospective

Facilitates post-epic retrospectives to extract lessons and prepare next epic planning.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-retrospective-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-retrospective
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-retrospective
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-retrospective-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After completing an epic, teams often skip structured reflection, losing valuable lessons and repeating mistakes. This Skill runs a guided, multi-agent retrospective that reviews completed stories, checks follow-through on previous action items, and prepares the team for the next epic. ## Core Features & Use Cases - Epic Discovery and Verification: Detects the completed epic from sprint-status.yaml, verifies story completion, and warns when running a retrospective on an incomplete epic. - Deep Story Analysis: Mines story files for dev notes, review feedback, lessons learned, technical debt, and recurring patterns across the epic. - Continuity Tracking: Loads the previous epic's retrospective and scores action items as completed, in progress, or not addressed. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and lists preparation gaps. - Use Case: After finishing Epic 3 of a game project, ask for a retrospective; the Skill facilitates a party-mode discussion with roles like Product Owner, Senior Dev, and QA, then produces a retrospective document with lessons and action items. ## Quick Start Ask the assistant to run a retrospective for the epic you just completed, for example by saying "run a retrospective for epic 3".

Frequently Asked Questions about gds-retrospective

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

FAQPage Schema
How do I run a retrospective for a completed epic?

Say "run a retrospective" or "let's retro the epic" and the Skill detects the completed epic from sprint-status.yaml. You confirm the epic number, then it guides a structured team discussion and produces a retrospective document.

What inputs does the retrospective workflow need?

It reads sprint-status.yaml, story files from the implementation artifacts folder, and planning documents like epics, architecture, and the GDD. It also loads the previous epic's retrospective if one exists to check action item follow-through.

Can I run a retrospective if the epic is not fully complete?

Yes, but the Skill warns you first and lists pending stories. You can choose to complete remaining stories, run a partial retrospective, or refresh sprint planning instead.

How does the retrospective track previous action items?

It loads the prior epic's retrospective file and marks each committed action item as completed, in progress, or not addressed based on evidence in the current epic's story records.

What output does the retrospective produce?

It generates a retrospective analysis document containing delivery metrics, lessons learned, pattern analysis across stories, action items with clear ownership, and preparation notes for the next epic.