learn

Aggregate and organize project learnings across sessions via gstack.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill learn-misstully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/MissTully/Gstack/tree/main/learn
Command: npx skills add https://github.com/MissTully/Gstack --skill learn-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregate and organize project learnings across sessions to preserve institutional knowledge.

Core Features & Use Cases

  • Review past learnings and prune stale notes to keep a compact knowledge base.
  • Search across sessions to surface patterns and decision rationales.
  • Export learnings into reports or documents for sharing with stakeholders.
  • Real-world use: after a project retro, export a 1-page learnings summary for the team.

Quick Start

Ask me to show learnings or export a summary.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I capture and organize project learnings across multiple sessions?

You can capture and organize project learnings across sessions by using a dedicated learnings store to aggregate institutional knowledge. This preserves decision rationales and team knowledge for future review.

What is the best way to search past project decisions and surface patterns?

The best way to search past project decisions is to query an aggregated learnings knowledge base. This surfaces historical patterns and rationales across sessions without manual digging.

How do I export a retrospective summary to share with stakeholders?

To export a retrospective summary, you can generate a compiled report from your stored learnings. This creates a shareable document of past decisions for stakeholders.

Can I prune stale notes to keep my knowledge base compact?

Yes, you can prune stale notes to maintain a compact knowledge base. Reviewing and removing outdated items ensures your institutional knowledge stays relevant and actionable.

Does this approach work for preserving institutional knowledge for engineering teams?

Yes, preserving institutional knowledge works effectively for engineering and product teams. It aggregates technical learnings and past decisions to prevent repeated mistakes across sessions.