distilling-lessons

Capture non-obvious resolved work insights as commit-anchored, standardized project lessons.

63|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/xhyqaq/superpowers-plus --skill distilling-lessons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distilling-lessons
Source: https://github.com/xhyqaq/superpowers-plus/tree/main/skills/distilling-lessons
Command: npx skills add https://github.com/xhyqaq/superpowers-plus --skill distilling-lessons

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When developers fix non-obvious bugs, make architectural decisions, or update interface contracts, the context and insights behind these resolutions often fade once the work is done, leading to repeated mistakes, wasted investigation time, and inconsistent project knowledge across team members and AI coding agents.

Core Features & Use Cases

  • Judgment-Gated Filtering: Automatically filters out trivial, non-reusable changes to only record high-value lessons that would change a future agent's approach to a similar problem.
  • Commit-Anchored Verification: Enforces that every lesson is tied to a verified 40-character git commit hash, ensuring all recorded insights are tied to proven, working solutions.
  • Standardized Lesson Formatting: Provides a mandatory template with sections for situation, root cause, actionable rules, and application boundaries, so lessons are readable and actionable for future agents reading them without context.
  • Use Case: After your team spends 3 hours debugging a non-obvious race condition in the payment processing flow, use this skill to record the root cause, avoidance rule, and commit hash so no future agent wastes time on the same issue.

Quick Start

Use the distilling-lessons skill to record the root cause and avoidance rule for the recent authentication timeout bug you fixed, anchored to its verified git commit.

Frequently Asked Questions about distilling-lessons

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

FAQPage Schema
How do I capture non-obvious bug fix root causes as reusable project memory?

To capture bug fix root causes as reusable project memory, record the verified root cause, actionable avoidance rules, and a 40-character git commit hash using a standardized lesson template to prevent future investigation time loss.

When should I record architectural decisions for agent knowledge reuse?

Record architectural decisions for agent knowledge reuse when resolutions involve non-obvious trade-offs, interface contract changes, or recurring pitfalls that would change a future agent's approach to a similar problem.

Do I need a git commit hash to document architectural decisions and bug fixes?

Yes, you need a verified 40-character git commit hash to document architectural decisions and bug fixes, ensuring every recorded lesson is anchored to a proven, working solution rather than unverified or trivial changes.

What is the best way to prevent repeated mistakes from non-obvious race conditions?

The best way to prevent repeated mistakes from non-obvious race conditions is applying judgment-gated filtering to record only high-value insights, formatting them with situation, root cause, and application boundaries for cold readability.

Does this lesson capturing method filter out trivial changes automatically?

Yes, this lesson capturing method applies judgment-gated filtering to automatically filter out trivial, non-reusable changes, ensuring only high-value lessons that change a future agent's approach are actually recorded.

Why format project memory lessons with standardized templates?

Format project memory lessons with standardized templates to provide mandatory sections for situation, root cause, actionable rules, and application boundaries, ensuring lessons remain readable and actionable for future agents reading them without context.