skills.rest
f4irline
f4irlineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

learnings

Append timestamped learning entries to categorized docs/learnings markdown files.

5|Updated Jan 25, 2026
Search Tags:#documentation#decisions#patterns#learnings#gotchas#knowledge-sharing#discoveries
One-click install
npx skills add https://github.com/f4irline/bbqparty-ai --skill learnings-f4irline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learnings
Source: https://github.com/f4irline/bbqparty-ai/tree/main/packages/opencode/.opencode/skills/learnings
Command: npx skills add https://github.com/f4irline/bbqparty-ai --skill learnings-f4irline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and preserves informal tribal knowledge, gotchas, patterns, decisions, and discoveries so future work avoids repeated investigation and duplicate mistakes.

Core Features & Use Cases

  • Structured Recording: Standardizes how learnings are written and appended to docs/learnings/ so entries are consistent and discoverable.
  • Categorization Guidance: Provides clear categories (gotchas, patterns, decisions, discoveries) and rules for choosing the primary category.
  • Onboarding & Research: Helps engineers scan relevant learnings when starting tickets, performing planning, or writing postmortems.

Quick Start

Append a concise learning entry for ticket STU-15 to docs/learnings/discoveries.md including a title, ticket reference, date, and a brief explanation of the insight.

Frequently Asked Questions about learnings

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

FAQPage Schema
How do I document project learnings and development discoveries to prevent repeated mistakes?▼

You can document project learnings by appending timestamped entries to markdown files in docs/learnings/. This standardizes how tribal knowledge and discoveries are recorded so future work avoids duplicate investigation.

What is the best way to categorize gotchas, patterns, and decisions during a project postmortem?▼

Categorizing learnings involves choosing a primary category such as gotchas, patterns, decisions, or discoveries, then appending the entry to the corresponding markdown file under docs/learnings/ with a standardized header.

How do I record a specific learning tied to a ticket reference?▼

To record a ticket-specific learning, append a concise entry to the relevant markdown file including the ticket reference, date, title, and a brief explanation of the insight using the standardized format.

Can I use this to help engineers onboard by scanning relevant past discoveries?▼

Yes, engineers can scan the structured learning entries in docs/learnings/ during onboarding, planning, or research to quickly find relevant discoveries, patterns, and gotchas tied to specific tickets.

Does this knowledge-sharing approach require any external dependencies or components?▼

No external dependencies or components are required. The approach works by appending timestamped entries to standard markdown files within your existing project documentation directory structure.

Related Skills

Explore More Software Engineering Skills→
whjelmarwhjelmar

memory-knowledge

Manage persistent topic-based knowledge files in markdown with an index.

Community
Intermediate
greyhaven-aigreyhaven-ai
29

Incident Response Skill

Automate incident response with runbooks, root cause analyses, and postmortem documentation.

Community
Basic
cy-walicy-wali

kb-article

Draft publish-ready knowledge base articles from resolved support issues.

Community
Intermediate
alexanderopalexanderop

writing-style

Apply ten style rules to refine prose in notes, blogs, and documentation.

Community
Basic