rcode-retrospective

Turn story records and project artifacts into a structured retrospective with owned action items.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-retrospective
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-retrospective
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams run a structured retrospective after an epic is finished, turning completed work into clear lessons, accountable action items, and preparation guidance for the next phase.

Core Features & Use Cases

  • Epic Review Facilitation: Guides a retrospective conversation with psychological safety, no-blame framing, and balanced participation.
  • Cross-Artifact Analysis: Reads completed stories, sprint status, prior retrospectives, and planning context to surface recurring patterns and root causes.
  • Actionable Outcomes: Produces owned action items with deadlines, captures lessons learned, and saves the final retrospective in the project workspace.
  • Use Case: A project lead asks for a retro on the last completed epic, and the Skill consolidates delivery wins, challenges, follow-up commitments, and next-epic readiness into one report.

Quick Start

Ask the rcode retrospective skill to run a retrospective for the completed epic and generate the final markdown report with owned action items.

Frequently Asked Questions about rcode-retrospective

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

FAQPage Schema
How do I run a retrospective for completed software epics?

An epic retrospective analyzes completed stories and sprint status to identify recurring patterns and root causes. It consolidates delivery wins, challenges, and follow-up commitments into a durable markdown report for the project workspace.

How do I track action items from a sprint retrospective?

Tracking retrospective action items requires assigning ownership and deadlines to each commitment. The Skill generates a durable markdown report with completion status checks, ensuring accountability and state synchronization for software delivery teams.

What is the best way to prepare for the next epic after delivery?

Preparing for the next epic involves comparing completed work against previous retrospective commitments. This cross-artifact analysis surfaces recurring patterns and generates next-epic readiness guidance within the final retrospective report.

Can I facilitate a no-blame retrospective using existing project artifacts?

Yes, you can facilitate a no-blame retrospective by reading prior planning context and story records. The Skill guides balanced participation and psychological safety while turning completed work into structured lessons and accountable action items.

Does this retrospective process work for agile software delivery teams?

Yes, this retrospective process is designed specifically for software delivery teams. It analyzes sprint status and epic artifacts to compare against previous commitments, producing owned action items and next-epic readiness in a durable markdown format.