retrospecting

Guide end-of-session retrospectives to surface and record actionable process improvements.

Updated Aug 23, 2026

Search Tags:#retrospective #process-improvement #action-items #continuous-improvement #team-workflow #log-review

Ready to run

npx skills add https://github.com/blackjiro/dotfiles --skill retrospecting-blackjiro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospecting
Source: https://github.com/blackjiro/dotfiles/tree/main/dot_claude/skills/retrospecting
Command: npx skills add https://github.com/blackjiro/dotfiles --skill retrospecting-blackjiro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables structured session retrospectives to surface and record actionable process improvements, helping teams learn from recent work and continually optimize their workflow.

Core Features & Use Cases

Structured Retro Workflow: Guides end-of-session reviews to identify non-efficient steps, recurring issues, and opportunities for improvement.
Action Item Generation: Produces concrete actions and follow-up tasks to close gaps and strengthen future sessions.
Usage Scenario: When finishing a software development sprint or research cycle, run this skill to review logs, assemble improvement points, and decide concrete actions, then log results for future reference.

Quick Start

Run the retro command to begin the end-of-session review and surface improvement points. Then review past logs, validate findings with the team, and assign follow-up actions.

Frequently Asked Questions about retrospecting

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

FAQPage Schema

How do I run a structured session retrospective to find process improvements?▼

To run a structured session retrospective, execute a retro command to review end-of-session logs, identify non-efficient steps and recurring issues, and list concrete process improvements for future workflows.

What is the best way to turn retrospective logs into actionable items for team workflow?▼

The best way to turn retrospective logs into actionable items is to review past session logs, validate findings with the team, and assign concrete follow-up actions that close workflow gaps and strengthen future sessions.

When do I need to perform an end-of-session retrospective for continuous improvement?▼

You need to perform an end-of-session retrospective when finishing a software development sprint or research cycle to surface recurring issues, record actionable improvements, and optimize team workflow continuously.

How does reviewing past retro logs help identify recurring issues in development workflows?▼

Reviewing past retro logs helps identify recurring issues by comparing historical session data against current development workflows, ensuring that previously recorded process improvements are validated and applied to new action items.

Can I use this retrospective approach for research cycles as well as software sprints?▼

Yes, you can use this retrospective approach for both software development sprints and research cycles, as it guides end-of-session reviews to surface inefficiencies and generate concrete actions across varying workflows.

Does session retrospective require any specific dependencies to record action items?▼

No specific dependencies are required to record action items, as the retrospective workflow operates directly on session logs to identify improvement opportunities and decide concrete actions without external tool integrations.