retro

Analyze project retrospectives to surface velocity, blockers, and improvement patterns.

Updated Apr 24, 2026

Search Tags:#timeline #retrospective #engineering #learnings #team #pattern-analysis #retro

Ready to run

npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill retro-sakshamkandel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill retro-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retro skill helps teams maintain a structured weekly engineering retrospective with persistent historical context, enabling recognition of accomplishments, trends, and actionable improvements across projects.

Core Features & Use Cases

Persistent retros: collect and render recent retros and learnings per project.
Timeline integration: surface recent milestones and shipping events to inform discussions.
Actionable outcomes: after each sprint, produce concrete improvements and follow-ups within the workspace.

Quick Start

Kick off a weekly retro by invoking the skill with the trigger "weekly retro" at the planned cadence and reference the project's retros directory to locate prior entries.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I run a weekly engineering retrospective with persistent historical context?▼

Run a weekly engineering retrospective by invoking the skill with the trigger "weekly retro" and pointing it to your project's retros directory to load prior entries. This surfaces past learnings and milestones to inform your current sprint review.

What is the best way to analyze project blockers and velocity trends across sprints?▼

Analyze project blockers and velocity trends by reviewing persistent retrospective files and timeline events. The skill surfaces patterns in blockers, velocity, and improvement opportunities across past sprints to guide actionable team discussions.

How does pattern analysis work for engineering learnings and timeline events?▼

Pattern analysis for engineering learnings works by operating across per-project retros files and timeline events to identify recurring trends. It surfaces prior entries and recent milestones to provide context for current sprint reviews and future planning.

Can I use this skill to generate actionable outcomes and follow-ups after a sprint?▼

Yes, you can generate actionable outcomes after each sprint. The skill produces concrete improvements and follow-ups within your workspace, using persistent context from prior retros to guide actionable discussions for future planning.

Do I need a specific directory structure to store retrospective markdown files?▼

You need a retros directory containing markdown files, typically structured as retros/*.md. The skill operates across these per-project retrospective files to locate prior entries, learnings, and milestones for context.

When should I not use an automated retrospective tool for sprint planning?▼

Avoid automated retrospective tools when your team lacks consistent markdown documentation or timeline event tracking. The skill requires persistent historical context across retros files to accurately surface patterns in velocity and blockers for future planning.