design-retrospective

Summarize design learnings from completed projects into retrospective documents.

234|55|Updated Mar 18, 2026

Search Tags:#retrospective #lessons-learned #design-process #design-memory #taste-profile #post-project

Ready to run

npx skills add https://github.com/Owl-Listener/designpowers --skill design-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-retrospective
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-retrospective
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospectives help teams reflect on a completed design project to extract learning and guide future decisions, turning experience into actionable knowledge.

Core Features & Use Cases

Structured reflection framework to audit decisions, taste evolution, and critique for future projects.
Generates a formal retrospective document that captures evidence, outcomes, and carry-forward actions to improve design-memory.
Use Case: After a shipped project, run a retrospective to identify what worked, what didn’t, and how to apply lessons to the next brief.

Quick Start

Initiate a retrospective after project completion to capture decisions, critique, and carry-forward learnings.

Frequently Asked Questions about design-retrospective

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

FAQPage Schema

How do I run a design retrospective after a project ships?▼

Run a design retrospective by gathering the design-state log, taste profile, and critique notes to generate a formal document capturing evidence, outcomes, and carry-forward lessons for future work.

What is a design retrospective and why do I need it?▼

A design retrospective is a structured reflection framework that audits decisions, taste evolution, and critique after project completion, turning design experience into actionable knowledge to guide future briefs.

When should I capture design lessons learned for future projects?▼

Capture design lessons learned after project verification, at end-of-sprint milestones, or whenever a team wants to review decisions, taste, and critique to improve design-memory.

What inputs are needed to document post-project design decisions and taste?▼

Documenting post-project design decisions requires gathering the design-state log, taste profile, and critique notes to summarize learnings and output a final retrospective document.

What's the best way to audit design taste evolution across completed sprints?▼

The best way to audit design taste evolution is using a structured retrospective framework that reviews critique notes and taste profiles from completed sprints to identify carry-forward actions.