skills.rest
vibbs
vibbsCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Generate a post-ship retrospective document by tracing artifact lineage from PRD to launch.

6|1|Updated Feb 25, 2026
Search Tags:#project management#retrospective#post-mortem#continuous improvement#lessons learned#artifact analysis
One-click install
npx skills add https://github.com/vibbs/company-os --skill retrospective-vibbs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/vibbs/company-os/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/vibbs/company-os --skill retrospective-vibbs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ./tools/artifact/validate.sh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of conducting post-ship retrospectives by tracing artifact lineage, evaluating success metrics, and capturing lessons learned, ensuring continuous improvement.

Core Features & Use Cases

  • Artifact Lineage Tracing: Automatically follows the chain of documents from PRD to launch.
  • Success Metric Evaluation: Assesses feature performance against defined metrics.
  • Lesson Capture: Identifies and records actionable insights for future projects.
  • Use Case: After a new feature is deployed, use this Skill to generate a comprehensive retrospective document that details what went well, what didn't, and what the team learned, linking it back to the original product requirements.

Quick Start

Run the retrospective skill for the feature associated with PRD-001.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate a post-ship retrospective document for a launched feature?▼

Yes, artifact lineage tracing automatically follows the chain of documents from PRD to launch. By analyzing the linked PRD, RFC, QA reports, and launch briefs, the retrospective connects feature performance insights directly back to your original product requirements.

What's the best way to evaluate success metrics during a post-mortem?▼

Evaluating success metrics during a post-mortem involves assessing feature performance against metrics defined in your original artifacts. This Skill automates that evaluation by cross-referencing launch briefs and PRDs to identify what went well and capture actionable lessons for future projects.

Do I need artifact validation scripts to run a project retrospective?▼

Yes, artifact validation scripts are required dependencies for quality assurance when running a retrospective. These scripts ensure the integrity of the PRD, RFC, and QA report inputs before the Skill generates the final post-ship retrospective document.

How do I capture lessons learned for continuous improvement after deployment?▼

To capture lessons learned for continuous improvement, the Skill analyzes post-ship artifacts to identify and record actionable insights. It evaluates what went well and what didn't, detailing project execution outcomes to ensure future projects benefit from past performance.

Related Skills

Explore More Product & Management Skills→
GabeujinGabeujin

breakdown-test

Generate test strategies, task breakdowns, and QA plans for GitHub projects.

Community
Advanced
LerianStudioLerianStudio
205

pmo-retrospective

Capture portfolio-level lessons learned and produce retrospective artifacts.

Official
Advanced
lalulalilalulali
8

phase

Detect and update the current product pipeline phase with artifact tracking.

Community
Advanced
carson-sweetcarson-sweet
6

rollback-revert

Identify and execute deployment rollbacks via git reverts, artifact redeployment, or feature flag toggling.

Community
Advanced