gsd:extract-learnings
Extract decisions, lessons, patterns, and surprises from completed phase artifacts
Profile →npx skills add davepoon/buildwithclaude --skill extract_learnings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<objective> Extract structured learnings from completed phase artifacts (PLAN.md, SUMMARY.md, VERIFICATION.md, UAT.md, STATE.md) into a LEARNINGS.md file that captures decisions, lessons learned, patterns discovered, and surprises encountered. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/extract-learnings.md </execution_context> Execute the extract-learnings workflow from @${C
What does the gsd:extract-learnings skill do?
Extract decisions, lessons, patterns, and surprises from completed phase artifacts
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill extract_learnings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.