skills.rest
jacobrocks1212
jacobrocks1212COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Generate a structured retrospective plan from PHASES.md, SPEC.md, and git history.

Updated Aug 23, 2026
Search Tags:#planning#retrospective#phases#retro#workflow-improvement#spec-divergences
One-click install
npx skills add https://github.com/jacobrocks1212/claude-config --skill retro-jacobrocks1212
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jacobrocks1212/claude-config/tree/main/user/skills/retro
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill retro-jacobrocks1212

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospective analysis of completed work — identifies issues, incorrect assumptions, and workflow improvements. After writing the retro plan, it coordinates follow-on actions to propagate changes and surface corrective work where needed.

Core Features & Use Cases

  • Detect and summarize issues, deviations, and learning points from PHASES.md, SPEC.md, and commit history.
  • Generate a concrete retro plan, including a spec-divergences report and recommended improvements.
  • Coordinate minor divergences propagation to SPEC.md and annotate plan records for traceability.

Quick Start

Provide a completed retro plan for the identified feature by analyzing PHASES.md, SPEC.md, and git history for the target feature.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a retrospective plan from completed feature work?▼

To generate a retrospective plan, the Skill reads your PHASES.md, SPEC.md, and git history to surface spec divergences and produce a structured plan of actionable workflow improvements.

What is a spec divergence report and how does it help post-implementation analysis?▼

A spec divergence report identifies deviations between your original SPEC.md and the actual implementation captured in git history and PHASES.md, helping you track incorrect assumptions and workflow issues.

Can I use retrospective analysis to propagate minor divergences back to my spec?▼

Yes, the retrospective analysis coordinates the propagation of minor divergences back to SPEC.md and annotates plan records, ensuring traceability between your completed feature work and updated specifications.

What files do I need to run a structured retrospective on a completed feature?▼

You need a PHASES.md file tracking task evidence, a SPEC.md defining intended behavior, and accessible git history for the target feature so the retrospective can analyze divergences and improvement opportunities.

What's the best way to turn retrospective learnings into actionable improvements?▼

The best way is to analyze commit history and spec deviations from PHASES.md, then generate a concrete improvement plan that coordinates follow-on actions to surface corrective work and propagate necessary changes.

Related Skills

Explore More Software Engineering Skills→
NigarumOvumNigarumOvum

research-goal

Organize finance research by defining objectives, tracking criteria, and managing evidence.

Community
Advanced
tim-hubtim-hub
2

jira-ticket-analyzer

Fetch Jira ticket data and generate a structured development plan.

Community
Intermediate
bajajvinamrbajajvinamr

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced
lepahclepahc
1

kspec-reflect

Automate end-of-session reflections and export insights to the planning backlog.

Official
Intermediate