reflect

Guide structured reflection on software projects and generate a summary file.

3|1|Updated Jan 26, 2026

Search Tags:#project management #tech stack #retrospective #post-mortem #reflection #learnings

Ready to run

npx skills add https://github.com/CinderZhang/driver-plugin --skill reflect-cinderzhang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/CinderZhang/driver-plugin/tree/main/skills/reflect
Command: npx skills add https://github.com/CinderZhang/driver-plugin --skill reflect-cinderzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers systematically capture valuable lessons learned during a project, focusing on what worked, what didn't, and especially the retrospective of the tech stack used.

Core Features & Use Cases

Structured Reflection Prompts: Guides users through key areas like challenges, tech stack choices, and time allocation.
Actionable Insights: Generates a summary file (/product/reflect.md) documenting reusable patterns and future improvements.
Use Case: After completing a complex financial modeling tool, a developer uses this Skill to document why a specific charting library was difficult to integrate and what alternative would have been better, preventing future similar issues.

Quick Start

Use the reflect skill to capture learnings after completing the project.

Frequently Asked Questions about reflect

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

FAQPage Schema

How do I capture project learnings after completing a software development project?▼

To capture project learnings, you need a structured reflection process that identifies successes, challenges, and tech stack insights from completed project artifacts. This Skill guides you through analyzing these elements to generate reusable patterns for future outcomes.

What is a tech stack retrospective and how does it improve future projects?▼

A tech stack retrospective evaluates the frameworks and tools used in a completed project. It documents why specific choices caused integration challenges and what alternatives would have been better, preventing similar issues in future development.

How do I run a structured post-mortem for my software project?▼

Running a structured post-mortem involves analyzing completed project artifacts against guided prompts covering challenges, time allocation, and tech stack choices. It transforms your input into a summary file documenting actionable insights and areas for improvement.

Can I document reusable patterns from a complex software project without manual formatting?▼

Yes, by providing your project analysis as input, this Skill automatically generates a summary file at `/product/reflect.md`. This file documents the reusable patterns and future improvements identified during your structured reflection.

Does project reflection require specific framework dependencies to analyze my development outcomes?▼

No, this project reflection process requires no external dependencies. It functions by prompting you for input based on your completed project artifacts, making it compatible with any software engineering tech stack you used.

When should I not use a structured project retrospective?▼

You should avoid a structured project retrospective if you lack completed project artifacts to analyze. The reflection process requires you to provide specific input regarding your development challenges and tech stack choices to generate actionable insights.