skills.rest
nagashima-toru
nagashima-toruCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Documents work learnings and improvements into .retrospectives for reuse.

Updated Jan 3, 2026
Search Tags:#documentation#retrospective#reflection#process-improvement#team-work#lessons-learned#automation-ideas
One-click install
npx skills add https://github.com/nagashima-toru/sandbox-claude-code --skill retrospective-nagashima-toru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/nagashima-toru/sandbox-claude-code/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/nagashima-toru/sandbox-claude-code --skill retrospective-nagashima-toru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct a retrospective after completing Epic, Story, task, or session. Document learnings, improvements, and propose automation/new skills by saving into the .retrospectives directory to enable continuous improvement.

Core Features & Use Cases

  • Collect structured reflections on what went well, what didn’t, and lessons learned.
  • Propose automation, new skills, and process improvements; organize results by Epic/Story and sessions.
  • Provide a repeatable workflow to reference in future projects and share with the team.

Quick Start

Run the retrospective tool to capture the current work's learnings and save a structured report in .retrospectives.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I document lessons learned after completing a software project epic?▼

Documenting lessons learned after a software epic involves capturing structured reflections on what went well, what didn't, and improvements, saving the record into a .retrospectives directory organized by epic or story for future reference.

What is the best way to capture process improvements and automation ideas from team workflows?▼

Capturing process improvements involves running a retrospective that collects structured inputs on lessons learned and proposes new automation ideas, storing them as a reusable record within your project's .retrospectives directory.

Can I organize retrospective records by individual stories or tasks instead of just epics?▼

Yes, retrospective records can be organized by individual stories or tasks. The tool structures saved reflections under the .retrospectives directory using a per-epic or per-story organization to maintain clear project documentation.

How do I create a repeatable workflow for team reflections across multiple sessions?▼

Creating a repeatable workflow for team reflections involves running the retrospective tool after each session to systematically document what went well and improvements, generating a structured report in .retrospectives to share with the team.

Do I need any specific dependencies to document post-work learnings in my project?▼

No specific dependencies are required to document post-work learnings. You can run the retrospective tool directly in your software project environment to save structured inputs and improvements without external components.

Related Skills

Explore More Education & Research Skills→
hanzlahabibhanzlahabib
2

rcode-retrospective

Turn story records and project artifacts into a structured retrospective with owned action items.

Community
Advanced
Gaku52Gaku52
6

lessons-learned

Capture and organize incident lessons into a centralized knowledge base.

Community
Advanced
marcmontecalvomarcmontecalvo

bmad-sprint-planning

Parse epic and story documentation to generate sprint-status.yaml files.

Community
Advanced
LerianStudioLerianStudio
205

pmo-retrospective

Capture portfolio-level lessons learned and produce retrospective artifacts.

Official
Advanced