whip-lesson-learn

Document whip runs as structured Markdown case studies under .whip/lesson-learn/.

10|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/bang9/ai-tools --skill whip-lesson-learn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: whip-lesson-learn
Source: https://github.com/bang9/ai-tools/tree/main/whip/skills-codex/whip-lesson-learn
Command: npx skills add https://github.com/bang9/ai-tools --skill whip-lesson-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures real whip runs as reusable case studies and lessons learned to preserve context for future reference.

Core Features & Use Cases

  • Create or update a Markdown file under .whip/lesson-learn/ with a canonical structure that documents prompts, decisions, outcomes, and IRC coordination.
  • Preserve concrete artifacts such as user prompts, tools used, branch/PR details, decision points, and final results to enable postmortems and knowledge sharing.
  • Supports multilingual writing rules and generates a concise, shareable case study ready for review.

Quick Start

Provide a file name for the lesson-learn entry, or allow the system to derive a date-based name, and I will generate the .whip/lesson-learn/<file-name>.md with a complete, sections-based template.

Frequently Asked Questions about whip-lesson-learn

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

FAQPage Schema
How do I document a postmortem for a whip run with prompts, decisions, and IRC coordination?▼

To document a whip run postmortem, the Skill generates a structured Markdown file under .whip/lesson-learn/ that captures prompts, decisions, outcomes, tools used, and IRC highlights into a reusable case study.

What is the best way to capture lessons learned from case studies into structured Markdown?▼

Capturing lessons learned from case studies is done by applying a fixed Markdown template that records prompts, actions, results, and decision points, preserving concrete artifacts for future postmortems and knowledge sharing.

How do I create a lesson-learn entry and what file naming conventions are supported?▼

To create a lesson-learn entry, provide a file name or let the system derive a date-based name, and it will generate the .whip/lesson-learn/<file-name>.md with a complete, sections-based template.

Does the lesson capture process support multilingual writing rules for generating case studies?▼

The lesson capture process supports language-specific translation rules when generating content, ensuring the case study and lessons learned are written according to multilingual conventions.

What specific artifacts are preserved when documenting whip sessions for postmortems?▼

Documenting whip sessions preserves concrete artifacts such as user prompts, tools used, branch and PR details, decision points, and final results to enable postmortems and knowledge sharing.

Can I use this lesson capture tool without any external dependencies?▼

The lesson capture tool operates without external dependencies, using only a fixed Markdown structure to store whip session documentation and IRC coordination highlights under the .whip/lesson-learn/ directory.