retro

Aggregate Jira stories and git activity into a structured sprint retrospective.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill retro-scripsteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Scripsteam/scrips-stack/tree/main/retro
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill retro-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint retrospectives help teams capture what shipped, what broke, and what was learned, turning insights into actionable improvements for the next sprint.

Core Features & Use Cases

  • Pull sprint data from Jira and git to generate a comprehensive retrospective
  • Provide sections: What shipped, What didn't ship, What broke, What we learned, and commitments for the next sprint
  • Facilitate honest, constructive feedback with concrete action items

Quick Start

Generate a sprint retrospective from Jira and Git data for the current sprint.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a sprint retrospective from Jira and git activity?▼

Generate a sprint retrospective by aggregating Jira stories and git activity for the current sprint. The Skill pulls sprint data from both sources to surface shipped work, blockers, and lessons learned in a structured format.

What sections should an agile sprint retrospective include?▼

An agile sprint retrospective should include sections for What shipped, What didn't ship, What broke, What we learned, and recommended process commitments. This format turns sprint outcomes into actionable improvements for the next sprint.

Can I do a mid-sprint process check using Jira and git data?▼

Yes, you can perform mid-sprint process checks by applying the retrospective format to current Jira stories and git activity. It surfaces what has shipped so far, ongoing blockers, and early lessons learned before the sprint ends.

Does this retrospective approach work without additional dependencies?▼

Yes, this retrospective approach works without additional dependencies. It operates standalone to aggregate Jira and git data, requiring no external components or modules to generate the structured retrospective output.

What's the best way to turn sprint outcomes into actionable process improvements?▼

The best way to turn sprint outcomes into actionable improvements is to aggregate Jira and git data into a structured retrospective. It identifies what broke and what was learned, then recommends concrete process commitments for the next sprint.