learning-harvest

Capture and synthesize operational learnings into a centralized, user-curated document.

176|13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/techygarg/lattice --skill learning-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learning-harvest
Source: https://github.com/techygarg/lattice/tree/main/plugins/lattice/skills/learning-harvest
Command: npx skills add https://github.com/techygarg/lattice --skill learning-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and synthesize operational learnings from practice into a centralized, user-curated document.

Core Features & Use Cases

  • Provides a living repository of cross-cutting patterns discovered during work to inform future sessions.
  • Enforces user confirmation before adding entries, ensuring quality and relevance.
  • Supports load and harvest workflows to keep learnings aligned with current standards and project context.

Quick Start

Start a session, then say 'harvest learnings' to capture patterns for future work.

Frequently Asked Questions about learning-harvest

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

FAQPage Schema
How do I capture operational learnings during feature development?

Capture operational learnings by triggering a harvest workflow during feature development, design reviews, or post-mortems to synthesize cross-cutting patterns into a centralized document.

What is a knowledge-management approach for team workflows?

A knowledge-management approach for team workflows surfaces cross-cutting patterns from practice into a user-curated document, maintaining a versioned structure to inform future sessions.

Can I review entries before they are added to the documentation?

Yes, the system enforces explicit user confirmation before writing entries to the learning documentation, ensuring the captured patterns meet your quality and relevance standards.

How do I document patterns discovered during a project retrospective?

Document patterns from a project retrospective by loading existing learnings and harvesting new insights, which are synthesized into a versioned, centralized repository for future reference.

What's the best way to maintain team knowledge over time?

Maintain team knowledge over time by using a simple, versioned structure to store operational learnings, keeping the repository aligned with current standards through load and harvest workflows.