retrospective

Name: retrospective
Availability: InStock
Author: kristopherlb

Create structured checkpoints and retrospective analyses to document project learnings and improvements.

Updated Feb 15, 2026

Search Tags:#project management #code analysis #developer workflow #retrospective #continuous improvement #checkpoint

Ready to run

npx skills add https://github.com/Kristopherlb/shinobi-wan --skill retrospective-kristopherlb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Kristopherlb/shinobi-wan/tree/main/.cursor/skills/retrospective
Command: npx skills add https://github.com/Kristopherlb/shinobi-wan --skill retrospective-kristopherlb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams capture project learnings, reduce repeated friction, and prevent plans from drifting away from actual implementation by creating structured checkpoints and retrospectives.

Core Features & Use Cases

Checkpoint Creation: Records progress, decisions, blockers, learnings, and alignment updates during long-running projects.
Retrospective Analysis: Guides systematic reviews of code quality, testing, documentation, workflows, and architecture to identify actionable improvements.
Pattern and Improvement Tracking: Converts recurring problems into reusable fixes through documented patterns, recommendations, and capability improvements.
Use Case: After completing an infrastructure feature, use this Skill to analyze what changed, identify process improvements, and create durable guidance for future development sessions.

Quick Start

Use the retrospective skill to create a checkpoint for the current project with progress, friction points, and proposed improvements.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I capture project learnings and prevent plans from drifting during development?▼

Capture project learnings by creating structured checkpoints that record progress, decisions, and blockers to prevent plans from drifting. These checkpoints maintain alignment between planning and actual implementation throughout long-running software development workflows.

What is a structured retrospective analysis for software development?▼

A structured retrospective analysis systematically reviews code quality, testing, documentation, workflows, and architecture to identify actionable improvements. It converts recurring project friction into documented patterns and durable guidance for future development sessions.

How do I track recurring process improvements and code friction points?▼

Track recurring process improvements by converting friction points into reusable fixes through documented patterns and recommendations. This maintains a tracking mechanism that records progress and identifies systemic issues across milestone reviews.

When do I need to create a checkpoint for a project milestone review?▼

Create a checkpoint during long-running projects when you need to record progress, decisions, blockers, and alignment updates. Checkpoints are essential for milestone reviews and planning alignment in continuous improvement scenarios.

Does this retrospective workflow require specific project management dependencies?▼

No specific project management dependencies are required. The workflow relies on organized templates, analysis workflows, and tracking mechanisms to document progress and identify friction within your existing software development environment.

What's the best way to analyze infrastructure feature changes after completion?▼

Analyze infrastructure feature changes by running a retrospective to review what changed, identify process improvements, and create durable guidance. This systematic review captures learnings and prevents repeated friction in future development sessions.