code-project-retrospective

Generate structured markdown retrospectives with metrics and verification checks.

Updated Aug 27, 2026

Search Tags:#quality assurance #retrospective #lessons learned #retrospective-report #project reflection

Ready to run

npx skills add https://github.com/kpachhai/idea-forge --skill code-project-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-project-retrospective
Source: https://github.com/kpachhai/idea-forge/tree/main/skills/code-projects/code-project-retrospective
Command: npx skills add https://github.com/kpachhai/idea-forge --skill code-project-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the lack of structured, durable reflection on completed development phases, enabling teams to document lessons learned and process insights systematically.

Core Features & Use Cases

Structured Retrospective Generation: Produces detailed markdown summaries including metrics, patterns, surprises, and areas for improvement after each phase.
Verification & Validation: Incorporates explicit verify-before-done checks and assessments of unverified items, ensuring quality.
Use Case: After completing a software development phase, a team runs this Skill to generate a comprehensive retrospective report that informs future planning and promotes process improvements.

Quick Start

Run the retrospection skill on your completed development phase directory to generate the structured reflection report.

Frequently Asked Questions about code-project-retrospective

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

FAQPage Schema

How do I generate a structured retrospective report for a completed software development phase?▼

To generate a structured retrospective report, run the Skill on your completed development phase directory. It produces a detailed markdown summary including project metrics, lessons learned, and verification checks to inform future planning.

What is the best way to document lessons learned and process improvements after a project phase?▼

The best way to document lessons learned is using a structured retrospective Skill that systematically captures project metrics, patterns, and areas for improvement into a durable markdown summary.

Does the retrospective process include quality assurance and verification checks?▼

Yes, the retrospective process includes quality assurance by incorporating explicit verify-before-done checks and assessing unverified items to ensure development quality before finalizing the report.

Can I use this retrospective tool for any completed development phase?▼

Yes, you can use this retrospective tool for any completed development phase. It analyzes project-specific data to produce comprehensive reflection reports that support continuous improvement in your workflows.

How do retrospective reports help with continuous improvement in development workflows?▼

Retrospective reports drive continuous improvement by systematically documenting lessons learned, identifying patterns and surprises, and verifying quality issues, which directly informs and refines future development planning.