gsd-extract-learnings

To extract learnings from completed project artifacts, analyze PLAN, SUMMARY, VERIFICATION, UAT, and STATE files to distill decisions, lessons, patterns, and surprises into a structured LEARNINGS.md record. This preserves hard-won context for future work phases.

Capturing decisions and lessons learned in a retrospective involves scanning completed phase artifacts to identify important choices, why they were made, and what worked or failed. This consolidates workflow history into a durable learnings document for future reference.

Yes, you can consolidate workflow history across multiple project state files by analyzing PLAN, SUMMARY, VERIFICATION, UAT, and STATE artifacts together. This extracts recurring patterns and unexpected findings into a single structured learnings summary.

You need to generate a LEARNINGS.md file during end-of-phase project retrospectives or delivery reviews. It serves as a durable record of decisions, lessons, and patterns extracted from completed artifacts before starting new work phases.

No, extracting learnings does not alter your existing workflow context or phase artifacts. The process strictly reads completed files to produce a durable LEARNINGS.md record without prematurely modifying the original workflow context.

A useful project retrospective document should include extracted decisions, lessons learned, recurring patterns, and unexpected surprises gathered from phase artifacts. This structured learnings record ensures valuable context is preserved for future work.