gsd-extract-learnings

Extracts decisions, lessons, patterns, and surprises from phase artifacts into a LEARNINGS.md document.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-extract-learnings-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-extract-learnings
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-extract-learnings
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-extract-learnings-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts completed phase artifacts into a clear, reusable set of learnings so you can improve future planning instead of rereading everything from scratch.

Core Features & Use Cases

  • Decision capture: Surfaces what was decided and why from artifacts like PLAN, SUMMARY, VERIFICATION, UAT, and STATE.
  • Lessons and patterns: Highlights repeatable behaviors, constraints, and effective approaches that emerged during execution.
  • Surprises and risks: Records unexpected outcomes and friction points so they can inform next phases.
  • Use case: After finishing a product or project phase, you can generate a LEARNINGS.md that you can reuse during the next iteration to reduce mistakes and accelerate alignment.

Quick Start

Run the extract-learnings workflow end-to-end at the path given in the skill context to produce a LEARNINGS.md from the completed phase artifacts.

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 learnings from completed project phase artifacts?

To extract learnings from phase artifacts, run the extract-learnings workflow to read completed files like PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md, generating a consolidated LEARNINGS.md document.

What is decision mining from retrospective phase artifacts?

Decision mining from retrospective artifacts surfaces what was decided and why during execution by analyzing files like SUMMARY.md and STATE.md, turning historical context into structured, reusable lessons for future iterations.

Do I need specific markdown files to generate a project learnings document?

Yes, generating a project learnings document requires completed phase artifacts including PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, and STATE.md to ensure accurate extraction of decisions, patterns, and surprises.

How do I capture unexpected outcomes and risks from a completed delivery phase?

Capture unexpected outcomes and risks by running the extract-learnings workflow to process your phase artifacts, which identifies friction points and surprises and records them directly into the output LEARNINGS.md file.

Can I reuse lessons from previous iterations to improve future planning?

Yes, you can reuse lessons from previous iterations by referencing the generated LEARNINGS.md during the next phase, reducing mistakes and accelerating alignment by applying repeatable behaviors and patterns.