retro

Name: retro
Availability: InStock
Author: solitasroh

Generates PDCA retrospective reports and updates centralized learnings log from docs and state files.

2|1|Updated Mar 22, 2026

Search Tags:#documentation #retrospective #workflows #lessons #retro #pdca

Ready to run

npx skills add https://github.com/solitasroh/rkit --skill retro-solitasroh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/solitasroh/rkit/tree/main/skills/retro
Command: npx skills add https://github.com/solitasroh/rkit --skill retro-solitasroh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PDCA retrospectives after a completed project or feature are often unordered, leading to missed learnings and weak action items. This skill provides a structured, repeatable workflow to capture metrics, feedback, and lessons.

Core Features & Use Cases

Collect and summarize PDCA metrics from docs and state files to create a consistent retrospective narrative.
Document what went well, what could improve, and translate insights into concrete action items and lessons learned.
Generate output documents at docs/04-report/{feature}.retro.md and maintain a centralized learnings log at .rkit/state/learnings.json for future planning.

Quick Start

Execute a retrospective for a completed feature by running the retro command with the feature name plan, design, or report context.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate structured PDCA retrospectives for completed features?▼

Automate structured PDCA retrospectives by running the retro command with a feature name to aggregate metrics, outcomes, and learnings into a consistent narrative. It evaluates AI assistance and workflow adherence to generate actionable insights.

What is the best way to document lessons learned and action items after a project?▼

Document lessons learned by capturing what went well and areas for improvement, translating insights into concrete action items. Outputs are saved as markdown reports and centralized learnings logs for future planning and traceability.

How does a retrospective workflow aggregate state files and report documents?▼

A retrospective workflow aggregates data by collecting metrics and feedback from docs/04-report, state files, and the central learnings log to evaluate action-item quality and workflow adherence with clear provenance.

Can I run PDCA retrospectives across MCU, MPU, and WPF project teams?▼

Yes, you can run PDCA retrospectives across MCU, MPU, and WPF projects and teams. The workflow applies consistently to collect data, evaluate workflow adherence, and maintain centralized learnings logs.

Where are retrospective outputs and learnings logs saved for future traceability?▼

Retrospective outputs and learnings are saved to docs/04-report/{feature}.retro.md and .rkit/state/learnings.json. This ensures clear provenance and traceability for future planning cycles.