drive-retro

Reviews completed projects and extracts reusable lessons into reflection notes and wiki.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill drive-retro-hivgb1-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drive-retro
Source: https://github.com/hivgb1-ai/do-better-workspace-v2/tree/main/.claude/skills/drive-retro
Command: npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill drive-retro-hivgb1-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project ends, most people move on without capturing what they learned, so the same mistakes repeat and hard-won insights are lost. This Skill closes each project by reviewing its full trajectory and distilling lessons that compound into future work. ## Core Features & Use Cases - Trajectory Review: Reads the project's progress.md log end-to-end and reconstructs what actually happened, comparing intended goals against actual outcomes. - Lesson Extraction: Captures only time-saving lessons — tastes, pitfalls, working patterns, and process insights — with honest confidence levels, discarding obvious or redundant findings. - Compounding Storage: Routes lessons to the right places: a reflection note in 40-personal/44-reflections/, profile update suggestions for CLAUDE.md, and wiki accumulation delegated to the wiki-ingest skill. - Use Case: After shipping a workshop program, ask for a retrospective. The Skill reviews the whole project log, identifies that promotion was skipped again (a recurring pattern), writes a reflection note, and proposes a profile update so the next project starts smarter. ## Quick Start Ask the AI to run a retrospective on the finished project and extract the lessons learned.

Frequently Asked Questions about drive-retro

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

FAQPage Schema
How do I run a project retrospective with an AI assistant?

Ask the AI to review the finished project using phrases like "retrospective" or "extract lessons learned". The Skill reads the project's progress.md log, compares goals against actual outcomes, and produces a structured review with lessons.

What does a project retrospective skill extract from project logs?

It extracts four lesson types: tastes (choices made and why), pitfalls to avoid, patterns that worked, and process insights about workflow. Each lesson gets an honest confidence level, and obvious or redundant findings are discarded.

Where are retrospective lessons stored after review?

Lessons go to three places: a reflection note in 40-personal/44-reflections/, proposed updates to the CLAUDE.md profile (requiring human approval), and the knowledge wiki via the wiki-ingest skill for cross-project reuse.

What happens if the project log is too thin for a retrospective?

The Skill stops and reports that the record is too thin to support a review rather than fabricating a plausible narrative. It only writes facts grounded in the actual progress log and real events.

When should this retrospective step run in a project workflow?

It runs as the seventh and final stage, after the shipping stage (drive-ship). It marks the project status as complete in progress.md and can propose starting a follow-up project via the drive-frame skill.