capture-lessons

Generate PR descriptions, update lessons, backlog, and retrospectives for sprint wrap-up.

5|Updated Mar 9, 2026

Search Tags:#automation #workflow #retrospective #backlog #pr #sprint #lessons

Ready to run

npx skills add https://github.com/rbah31/claude-code-workflow --skill capture-lessons

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: capture-lessons
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/capture-lessons
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill capture-lessons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the sprint wrap-up process by closing the loop after a sprint. It creates the PR, documents lessons learned, updates the backlog, and prepares the retrospective.

Core Features & Use Cases

PR generation: automatically creates a descriptive PR summarizing sprint work.
Lessons capture: appends new lessons to tasks/lessons.md with proper formatting.
Backlog & docs updates: moves completed items to backlog-archive and updates sprint history and retrospectives.
End-of-sprint workflow: ideal for use at sprint end or when closing a sprint, after fixes and wrap-up prompts.

Quick Start

Run this skill at sprint end to generate the PR, update lessons.md, backlog, and retrospective.

Frequently Asked Questions about capture-lessons

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

FAQPage Schema

How do I automate sprint wrap-up tasks like PR descriptions and backlog updates?▼

Automating sprint wrap-up generates standardized PR descriptions, appends lessons to tasks/lessons.md, refreshes the backlog, and produces a retrospective by processing sprint folder artifacts like plan.md and build-output.md.

What is the best way to capture lessons learned at the end of a sprint?▼

Capturing sprint lessons involves appending new insights to tasks/lessons.md with proper formatting, ensuring sprint documentation and history are maintained alongside backlog archives and retrospective outputs.

How do I generate a PR description from sprint documentation files?▼

Generating a PR description from sprint documentation aggregates work summaries from build-output.md, review-output.md, fix-output.md, and redteam-output.md to create a standardized pull request summary for the sprint.

Does the sprint retrospective workflow require specific input files?▼

The sprint retrospective workflow processes existing sprint folder artifacts including plan.md, build-output.md, review-output.md, fix-output.md, redteam-output.md, and tasks/lessons.md to close the sprint loop.

When should I run sprint wrap-up automation to update the backlog and history?▼

Run sprint wrap-up automation at the end of a sprint or when closing a sprint, after fixes and wrap-up prompts are complete, to move completed items to backlog-archive and update sprint history.

Can I update multiple sprint artifacts like lessons.md and retrospectives simultaneously?▼

Updating multiple sprint artifacts simultaneously creates PR descriptions, appends lessons to tasks/lessons.md, moves completed items to backlog-archive, and generates retrospective documentation in one standardized workflow.