# Project Retrospective

> Synthesizes epic retros into project-retro.md. Use after project-validate when closing a project phase.

- Skill: `telum-ai/project-retrospective` (Agent Skill)
- Install (CLI): `npx skillmds@latest add telum-ai/project-retrospective`
- Raw SKILL.md: https://api.skillmd.com/api/skills/telum-ai/project-retrospective/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: telum-ai (https://skillmd.com/u/telum-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/telum-ai/project-retrospective

---


# project-retrospective

Read `.speck/templates/project/project-retro-template.md`, `project-validation-report.md`, current project truth, and every epic retro. Story retros have already been synthesized and are not primary inputs.

1. Compare the promised product with delivered outcomes, readiness evidence, effort, drift, and defect escape patterns.
2. Reconcile stale project truth before closing the retrospective.
3. Cross-epic recurrence validates a project-wide pattern. Maintain project-owned `.speck/patterns/learned/` only for evidence-backed rules with named consumers; keep narrower learning in its epic retro.
4. Route generalized Speck defects and improvements through `speck-feedback`, stripped of project secrets. Do not mutate Speck-managed methodology inside the product repo.
5. Fill `[PROJECT_DIR]/project-retro.md`, record concrete actions and remaining questions, and stamp it.