team-retro

Generate a structured retrospective with findings and update recommendations from post-ship artifacts.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/davekim917/bootstrap --skill team-retro-davekim917
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-retro
Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-retro
Command: npx skills add https://github.com/davekim917/bootstrap --skill team-retro-davekim917

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Post-ship learning capture. Analyzes workflow artifacts from a completed feature to extract stage-by-stage findings, key learnings, and recommended updates to CLAUDE.md and skills. Use after /team-ship completes. User-invoked, suggested by /team-ship completion message. Do not use mid-workflow or before shipping.

Core Features & Use Cases

  • Post-ship analysis to extract what worked, what was missed, and recommended updates to CLAUDE.md and skills.
  • Produces a retro document with actionable recommendations saved to docs/retros/<feature>/retro.md.
  • Guides updates to CLAUDE.md, workflow skills, and project skills.

Quick Start

Invoke /team-retro after /team-ship completes to generate a retrospective from available artifacts.

Frequently Asked Questions about team-retro

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

FAQPage Schema
How do I generate a post-ship retrospective from project artifacts?

To generate a post-ship retrospective, analyze completed feature artifacts in docs/specs/<feature>/ and git history to extract stage-by-stage findings, key learnings, and update recommendations.

When should I run a post-ship retro for feature development?

Run a post-ship retro only after a feature is completely shipped and /team-ship has finished. Do not use this process mid-workflow or before the final deployment artifacts exist.

How do I update CLAUDE.md based on team learnings after shipping?

Update CLAUDE.md by analyzing post-ship workflow artifacts to identify process improvements, then applying the structured update recommendations generated from the retrospective findings.

What should be included in a development retrospective document?

A development retrospective document should include stage-by-stage findings, key learnings, and update recommendations, with specific citations to the artifacts and git history analyzed.

Can I capture team learning mid-workflow before a feature ships?

No, you cannot capture post-ship team learning mid-workflow. Retrospective analysis requires completed features where shipping has finished and workflow artifacts exist for review.

Where are retrospective outputs saved when analyzing post-ship artifacts?

Retrospective outputs are saved as a structured retro.md document in the docs/retros/<feature>/ directory, containing actionable recommendations for updating project skills and workflow.