retrospective

Solid

Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.

AI & Automation 20,436 stars 2970 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Phase 1: Parse Arguments Determine whether this is a sprint retrospective (`sprint-N`) or a milestone retrospective (`milestone-name`). --- ## Phase 1b: Check for Existing Retrospective Before loading any data, glob for an existing retrospective file: - For sprint retrospectives: `production/retrospectives/retro-[sprint-slug]-*.md` (also check `production/sprints/sprint-[N]-retrospective.md` as an alternate location) - For milestone retrospectives: `production/retrospectives/retro-[milestone-name]-*.md` If a matching file is found, present the user with: ``` An existing retrospective was found: [filename] [A] Update existing retrospective — load it and add/revise sections [B] Start fresh — generate a new retrospective, archiving the old one ``` Wait for user selection before continuing. If updating, read the existing file and carry its content forward into the generation phase, revising sections with new data. --- ## Phase 2: Load Sprint or Milestone Data Read the sprint or milestone plan from the appropriate location: - Sprint plans: `production/sprints/` - Milestone definitions: `production/milestones/` **If the file does not exist or is empty**, output: > "No sprint data found for [sprint/milestone]. Run `/sprint-status` to generate > sprint data first, or provide the sprint details manually." Then use `AskUserQuestion` to present two options: - **[A] Provide data manually** — ask the user to paste or describe the sprint tasks, dates, and outcomes; ...

Details

Author
Donchitos
Repository
Donchitos/Claude-Code-Game-Studios
Created
3 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

11,758 Updated 1 weeks ago
phuryn
AI & Automation Solid

retro-analysis

Analyse sprint delivery data and produce a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/Stop/Continue prompts, and one concrete experiment for next sprint.

915 Updated 3 days ago
mohitagw15856
Testing & QA Listed

retrospective

Sprint retrospective with metrics and adaptive sizing

4 Updated today
lwalden
AI & Automation Listed

retro

Sprint or cycle retrospective — what shipped, what blocked, stakeholder feedback, learnings, next backlog. Use at end of a sprint or release cycle. Works for Scrum and Kanban.

0 Updated yesterday
yusufkaracaburun
AI & Automation Listed

retro

Run sprint close — aggregate per-task mini-retros, audit the backlog (HARD gate), classify findings into fix-now vs defer, fix process bugs immediately, write the full retro file, and move STATUS prose to STATUS-archive. Use when the user says '/retro', 'close the sprint', 'sprint retrospective', 'wrap up sprint XX'.

1 Updated today
Maximumsoft-Co-LTD