skills.rest
grigb
grigbCOMMUNITY
Explore all skills by this author →
Website𝕏@SpiritBitsGitHub

process-analysis-retrospective

Analyzes project evolution from git logs and documentation to generate retrospective reports.

4|Updated Dec 7, 2025
Search Tags:#retrospective#post-mortem#pattern-recognition#process-analysis#git-analysis#organizational-learning
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill process-analysis-retrospective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-analysis-retrospective
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-process-analysis-retrospective
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill process-analysis-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the loss of organizational memory by systematically analyzing project artifacts to identify patterns, root causes, and lessons learned that are often buried in git history and documentation.

Core Features & Use Cases

  • Process Archaeology: Reconstructs project timelines and decision points from git logs and documentation.
  • Pattern Extraction: Identifies recurring success and challenge patterns across technical, process, and human dimensions.
  • Use Case: After completing a complex API redesign, use this agent to analyze the evolution of the architecture, identify why certain pivots occurred, and generate a retrospective report that informs future development strategies.

Quick Start

Use the process-analysis-retrospective skill to analyze the evolution of the current project and generate a retrospective report.

Frequently Asked Questions about process-analysis-retrospective

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

FAQPage Schema
How do I analyze git history to extract lessons learned from a project?▼

To analyze git history and extract lessons learned, this Skill reconstructs project timelines and decision points from development artifacts to identify root causes and generate persistent retrospective reports.

What is the best way to run a retrospective on a complex software project?▼

The best way to run a software project retrospective is to systematically analyze project evolution and documentation to synthesize insights into persistent analysis files for future development strategies.

How do I reconstruct project timelines and decision points from git logs?▼

To reconstruct project timelines from git logs, this Skill performs process archaeology to trace project evolution and extract actionable patterns from development artifacts.

Can I generate a post-mortem report from project documentation and communication records?▼

Yes, you can generate a post-mortem report by analyzing project documentation and communication records to identify root causes and synthesize lessons learned into persistent analysis files.

Do I need access to git logs and communication records to identify root causes in a retrospective?▼

Yes, you need access to git logs, project documentation, and communication records to identify root causes and extract actionable patterns across technical, process, and human dimensions.

Related Skills

Explore More Software Engineering Skills→
grigbgrigb
4

process-analysis-retrospective-quick

Analyze git history and documentation to extract lessons learned and root causes.

Community
Advanced
BellaBeBellaBe
37

reasoning-counterfactual

Evaluate alternative decisions by simulating interventions on past or hypothetical futures.

Community
Advanced
mcampbellrmcampbellr

gsd-complete-milestone

Archives milestone artifacts and updates ROADMAP and REQUIREMENTS via git commit and tag.

Community
Advanced
neurofooneurofoo
106

postmortem

Facilitate blameless post-mortem incident analysis to identify root causes and define preventative action items.

Community
Intermediate