gsd-extract-learnings

Extract decisions, lessons, patterns, and surprises into a consolidated LEARNINGS.md file.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-extract-learnings-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-extract-learnings
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-extract-learnings
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-extract-learnings-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents valuable decisions, lessons, and surprises from being lost after a phase completes by consolidating them into a single, structured LEARNINGS.md artifact.

Core Features & Use Cases

  • Decision capture: Extracts explicit choices and rationale from completed artifacts such as PLAN.md and VERIFICATION.md.
  • Lesson & pattern mining: Identifies recurring issues, improvements, and successful approaches across the phase documentation.
  • Surprise detection: Surfaces unexpected outcomes and deviations that should inform future work.
  • Use case: After finishing a project phase, consolidate artifacts from planning through UAT into a durable summary that a team can reuse for the next iteration.

Quick Start

Run the extract-learnings workflow end-to-end using the phase-number you want to summarize, producing a LEARNINGS.md at the workflow’s configured location.

Frequently Asked Questions about gsd-extract-learnings

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

FAQPage Schema
How do I extract decisions and lessons from completed project phase artifacts?

Decision extraction pulls explicit choices and rationale from completed artifacts like PLAN.md and VERIFICATION.md, consolidating them into a single LEARNINGS.md file. It prevents valuable decisions and lessons from being lost after a phase completes.

What is the best way to run a retrospective on UAT analysis documentation?

Surprise detection in retrospective workflows surfaces unexpected outcomes and deviations from completed phase documentation. It consolidates these surprises into a LEARNINGS.md file, informing future work and preventing valuable deviations from being lost.

How do I consolidate end-of-phase wrap-ups into a single file?

Consolidate end-of-phase wrap-ups by running the extract-learnings workflow with a phase-number argument. This processes planning through UAT artifacts and produces a structured LEARNINGS.md file at the workflow's configured location.

What documents do I need before extracting learnings from a project phase?

You need completed phase artifacts including PLAN.md, SUMMARY.md, VERIFICATION.md, UAT, and STATE documents. These provide the explicit choices, recurring issues, and unexpected outcomes necessary to generate a consolidated LEARNINGS.md file.

Can workflow automation capture decision mining insights from phase outputs?

Workflow automation captures decision mining insights by executing the extract-learnings workflow on phase outputs. It identifies recurring patterns and rationale, consolidating them into a durable LEARNINGS.md artifact for team reuse.

When should I not use automated learnings extraction for documentation?

Avoid automated learnings extraction when phase artifacts are incomplete or missing required PLAN, SUMMARY, VERIFICATION, UAT, and STATE documents. The workflow depends on these completed inputs to accurately mine decisions, patterns, and surprises.