Guide structured reflection on software projects and generate a summary file.
npx skills add https://github.com/CinderZhang/driver-plugin --skill reflect-cinderzhang
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
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.
/product/reflect.md) documenting reusable patterns and future improvements.Use the reflect skill to capture learnings after completing the project.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
deltatreeAnalyzes completed stories and sprint status files to generate actionable improvement items for retrospectives.
chriswesttAggregate project learnings into a searchable index with structured tags.
yohayetsionGenerate structured team retrospective documents with action items and learnings.
alfredoperezDetect the Git remote URL for GitHub integration in SpecKit repositories.