gsd-extract_learnings

To extract learnings from project artifacts, this skill reads designated files like PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md, aggregating decisions, lessons, patterns, and surprises into a structured LEARNINGS.md file for rapid retrospectives.

The best way to consolidate scattered project decisions and lessons learned is by running an extraction workflow that reads your completed phase artifacts and formats the aggregated findings into a canonical LEARNINGS.md document.

Yes, you can use this to generate a learning brief from phase closeout documents. It surfaces key learnings from your project artifacts and writes them into a formatted LEARNINGS.md file, producing a shared brief for the team.

You can automate post-mortem documentation from existing markdown files by applying this skill to your retrospective cycles. It reads the designated phase artifacts and automatically writes a structured LEARNINGS.md containing the extracted decisions and surprises.

Yes, you need specific artifact files to run the extract learnings workflow. The process reads PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md to surface decisions and key learnings for your retrospective brief.

When formatting extracted project learnings, the generated LEARNINGS.md file includes structured sections specifically for decisions, lessons learned, patterns, and surprises aggregated from your phase artifacts.