learnings-synthesis

Synthesize cross-cutting patterns from a vertical's build cycle into learnings documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmbays/print-4ink --skill learnings-synthesis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learnings-synthesis
Source: https://github.com/cmbays/print-4ink/tree/main/.claude/skills/learnings-synthesis
Command: npx skills add https://github.com/cmbays/print-4ink --skill learnings-synthesis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a vertical's build cycle, this skill reads everything that happened — KB docs, PRs, reviews, registry entries, git history — and extracts patterns that improve future work. The output is a learnings KB doc and updates to CLAUDE.md Lessons Learned. This is not a summary of what was built. It's an extraction of how it was built and what that teaches us.

Core Features & Use Cases

  • Gather Sources: Read and cross-reference KB docs, the session registry, git history, and merged PRs for the target vertical.
  • Extract Patterns: Identify reusable approaches, data-flow patterns, and lessons across the vertical's lifecycle.
  • Produce Learnings: Draft a templated learnings document and apply updates to CLAUDE.md Lessons Learned, then commit changes.

Quick Start

Run learnings-synthesis after a vertical completes its build to generate the learnings KB and update CLAUDE.md.

Frequently Asked Questions about learnings-synthesis

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

FAQPage Schema
How do I extract reusable patterns from a build cycle after a vertical completes?

To synthesize learnings from a build cycle, you need sufficient documentation and completed build work as prerequisites. The process then aggregates KB docs, PRs, reviews, registry entries, and Git history to produce actionable learnings.

What is the difference between a build summary and synthesizing cross-cutting learnings?

Synthesizing cross-cutting learnings extracts how a vertical was built and what that teaches us, rather than summarizing what was built. It identifies reusable approaches and data-flow patterns across the lifecycle.

Do I need completed build work and documentation before running a learnings synthesis?

Yes, learnings synthesis requires sufficient documentation and completed build work as prerequisites. It is executed during the learnings phase or upon retrospection requests after a vertical completes its build.

How do I update CLAUDE.md Lessons Learned using retrospective patterns?

To update CLAUDE.md Lessons Learned, run learnings synthesis after a vertical completes. It drafts a templated learnings document, applies the updates to CLAUDE.md, and commits the changes.

What sources are needed to aggregate build-cycle learnings for a retrospective?

Aggregating build-cycle learnings requires KB docs, the session registry, git history, and merged PRs for the target vertical. These sources are cross-referenced to identify reusable approaches and lessons.