design-retrospective

Analyze completed design projects and generate structured retrospective reports.

Updated Apr 13, 2026

Search Tags:#retrospective #continuous improvement #design review #lessons learned #design process

Ready to run

npx skills add https://github.com/Angusatgithub/Charmera --skill design-retrospective-angusatgithub

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically review completed design projects to identify successes, failures, and insights, fostering continuous improvement.

Core Features & Use Cases

Comprehensive Analysis: Guides the collection of evidence, evaluation of decisions, and process quality for thorough retrospectives.
Documentation Preparation: Supports drafting detailed retrospective reports that capture lessons learned and design debt.
Use Case: After a major design phase, a team uses this Skill to document the process, analyze what worked, and plan improvements for the next project.

Quick Start

Describe the recent design project using this skill to generate a structured retrospective report.

Frequently Asked Questions about design-retrospective

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

FAQPage Schema

How do I conduct a structured design retrospective for my completed project?▼

A structured design retrospective requires collecting project evidence, evaluating design decisions, and reviewing process flow to generate a comprehensive report. This approach systematically identifies successes, failures, and design debt to foster continuous improvement for future projects.

What should be included in a design review to capture lessons learned?▼

A design review documenting lessons learned should include an analysis of design decisions, process quality, accumulated design debt, and taste evolution. Capturing these elements ensures teams can systematically evaluate outcomes and plan actionable process improvements.

Can I use this to document design debt after a major design phase?▼

Yes, you can document design debt after a major design phase by evaluating the project's process flow and decisions. This systematic review identifies specific design debt and captures lessons learned to enhance future design outcomes and process optimization.

What is the best way to analyze design decisions for continuous improvement?▼

The best way to analyze design decisions for continuous improvement is through a structured retrospective that guides evidence collection and process evaluation. This facilitates thorough analysis of what worked and what failed, directly enhancing future design outcomes.

Do I need to prepare project evidence before starting a design retrospective?▼

Yes, preparing detailed project evidence is required before starting a design retrospective. The process requires reviewing detailed evidence to accurately evaluate decisions, document process flow, and analyze design debt for the final retrospective report.