write-retrospective

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.

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.

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.

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.

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.

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.