write-retrospective

Draft a retrospective.md documenting outcomes, blockers, and actions for a sprint or epic.

1|Updated Apr 25, 2026

Search Tags:#documentation #routing #retrospective #delivery #sprint #epic

Ready to run

npx skills add https://github.com/daddia/space --skill write-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-retrospective
Source: https://github.com/daddia/space/tree/main/.agents/skills/write-retrospective
Command: npx skills add https://github.com/daddia/space --skill write-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a retrospective.md capturing what went well, what did not, and what to change for a sprint or epic. Routes insights to the correct delivery track. Use when the user mentions "write a retrospective", "sprint retro", "epic retrospective", "what did we learn", or "end of sprint reflection". Do NOT use to update product strategy — use refine-product. Do NOT use to collect delivery metrics — use write-metrics-report.

Core Features & Use Cases

Produces a structured retrospective.md that documents outcomes, blockers, and actions aligned to delivery tracks.
Routes each finding to the appropriate track (Delivery, Architecture, or Discovery) for follow-through.
Reuses backlog and related artefacts to contextualize actions and track drift over time.

Quick Start

Run this skill to generate a retrospective.md that records what went well, what did not, and concrete actions.

Frequently Asked Questions about write-retrospective

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

FAQPage Schema

How do I write a sprint retrospective that routes insights to delivery tracks?▼

To write a sprint retrospective, draft a retrospective.md capturing what went well, what did not, and what to change. Route each finding to the appropriate track (Delivery, Architecture, or Discovery) for follow-through and reuse backlog artefacts to contextualize actions.

What should be included in an end-of-sprint reflection document?▼

An end-of-sprint reflection document should include outcomes, blockers, and concrete actions aligned to delivery tracks. It captures what went well, what did not, and what to change, reusing related backlog artefacts to track drift over time and contextualize follow-up actions.

Can I use a retrospective to update my product strategy and metrics?▼

A retrospective focuses on delivery insights and cannot be used to update product strategy or collect delivery metrics. You must delegate product strategy updates to refine-product and delivery metrics collection to write-metrics-report to respect boundary constraints.

When should I use an epic retrospective instead of a sprint retrospective?▼

Use an epic retrospective for end-of-epic or end-of-phase reflections, while a sprint retrospective suits end-of-sprint reviews. Both produce a structured retrospective.md routing insights to Delivery, Architecture, or Discovery tracks for appropriate follow-through.

What is the best way to structure a retrospective.md for sprint delivery tracks?▼

The best way to structure a retrospective.md is by documenting outcomes, blockers, and actions aligned to delivery tracks. Route findings to Delivery, Architecture, or Discovery tracks and reuse backlog artefacts to contextualize actions and track drift over time.

Does this retrospective skill handle backlog drift tracking over multiple sprints?▼

Yes, retrospective generation reuses backlog and related artefacts to contextualize actions and track drift over time. It captures sprint or epic outcomes and routes insights to the correct delivery track to ensure follow-through on identified drift.