epic-retrospective

Synthesize story-retro.md files into epic-level pattern and issue validations.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill epic-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-retrospective
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/epic-retrospective
Command: npx skills add https://github.com/telum-ai/speck --skill epic-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of analyzing completed stories within an epic, identifying recurring patterns and issues, and applying those learnings to improve current and future projects and the Speck methodology itself.

Core Features & Use Cases

  • Synthesize Story Retrospectives: Aggregates insights from multiple story retrospectives into a cohesive epic-level summary.
  • Validate Patterns and Gotchas: Identifies systemic issues and reusable patterns that appear across multiple stories.
  • Apply Learnings: Updates future epic specifications, project-level documentation, and proposes improvements to Speck methodology commands and templates.
  • Use Case: After completing an epic with several stories, use this Skill to automatically find common development roadblocks encountered across those stories, document best practices that emerged, and update project documentation to reflect these new insights.

Quick Start

Run the epic-retrospective skill on the current epic to synthesize all story retrospectives and apply learnings.

Frequently Asked Questions about epic-retrospective

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

FAQPage Schema
How do I synthesize story retrospectives to identify recurring development roadblocks?

You can synthesize story retrospectives by processing story-retro files and epic artifacts to validate patterns, identify systemic issues across multiple stories, and document best practices that emerged.

What is the best way to validate systemic issues across a completed epic?

Validating systemic issues across an epic involves aggregating insights from multiple story retrospectives into a cohesive summary to find recurring gotchas and reusable patterns.

How do I apply retrospective learnings to improve project documentation?

Applying retrospective learnings updates future epic specifications and project-level documentation, while also proposing meta-level improvements to methodology commands and templates.

When do I need an epic-level retrospective process?

An epic-level retrospective process is needed after completing an epic with several stories, to automatically find common development roadblocks encountered across those stories.

Can I use this to prevent recurring gotchas in future sprints?

Yes, identifying systemic issues and reusable patterns across completed stories prevents recurring gotchas by updating documentation and applying learnings to current projects.

What prerequisites are needed to aggregate epic retrospective insights?

Aggregating epic retrospective insights requires completed story-retro files and epic artifacts as input to process and identify patterns for methodology improvement.