gsd-extract-learnings

To extract lessons learned from phase artifacts, review completed PLAN, SUMMARY, VERIFICATION, UAT, and STATE files to consolidate recurring decisions, tradeoffs, patterns, and surprises into a structured LEARNINGS.md document.

The best way to capture project decisions after a milestone is to consolidate choices and rationale from phase artifacts into a durable LEARNINGS.md record, ensuring key decisions and unexpected findings are not lost after delivery.

Yes, you can generate a retrospective document by reviewing PLAN and SUMMARY files alongside VERIFICATION, UAT, and STATE artifacts to faithfully extract notable tradeoffs and emerging patterns into a structured learnings document.

You do not strictly need VERIFICATION and UAT files, but applying this workflow to all available phase artifacts ensures a more faithful consolidation of recurring decisions and unexpected findings into your LEARNINGS.md.

A LEARNINGS.md file should include extracted decisions, rationale, lessons, repeatable patterns, notable tradeoffs, and unexpected surprises consolidated from completed phase artifacts to guide future project workflow improvements.

Teams lose decisions after delivery when phase artifacts are not consolidated into a durable record. Extracting choices, patterns, and surprises into a structured LEARNINGS.md preserves this knowledge for future reuse.