retro

Analyze completed Linear cycles to generate retrospective insights on velocity and scope.

142|19|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/joa23/linear-cli --skill retro-joa23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/joa23/linear-cli/tree/main/internal/skills/retro
Command: npx skills add https://github.com/joa23/linear-cli --skill retro-joa23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze completed Linear cycles for retrospectives to identify velocity trends, scope creep, and patterns to improve future planning.

Core Features & Use Cases

  • Velocity trend analysis across cycles
  • Detect scope creep and pattern-based improvements
  • Generate actionable insights for planning and process improvements

Quick Start

Run a retrospective analysis on the most recent cycles to generate a set of actionable insights.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate data-driven retrospective insights from Linear cycles?

To generate retrospective insights from Linear cycles, the Skill analyzes completed sprint data to identify velocity trends, scope creep, and process bottlenecks. It outputs actionable recommendations for future planning meetings.

What is the best way to track sprint velocity trends and scope changes?

Tracking sprint velocity trends and scope changes is done by analyzing historical cycle data across sprints. The Skill examines completed cycles to detect patterns in scope creep and generate reports on team performance over time.

Can I use cycle analysis to identify blockers in my team's sprints?

Yes, cycle analysis can identify blockers by examining completed sprint cycles for bottlenecks and pattern-based delays. The Skill processes historical cycle data to pinpoint recurring issues affecting team velocity.

How do I run a retrospective analysis on recent sprint cycles?

Running a retrospective analysis on recent cycles requires access to your completed Linear cycle data. The Skill processes this data to produce velocity charts, pattern reports, and recommended action items for planning improvements.

Do I need specific cycle data to detect scope creep in sprint planning?

Yes, you need access to completed Linear cycle data to detect scope creep effectively. The Skill analyzes historical cycle information to identify scope changes and pattern-based improvements for future sprint planning.

What actionable insights can I get from analyzing sprint bottlenecks?

Analyzing sprint bottlenecks yields actionable insights such as velocity trend reports, scope creep patterns, and recommended action items. These outputs help improve future planning meetings and overall team performance.