retro

Plans and executes structured phase-based retrospectives for work sessions.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill retro-joshsmithxrm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill retro-joshsmithxrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured retrospectives enable users to review recent work sessions, collect evidence, and surface patterns to drive improvement, rather than relying on memory or ad-hoc reflections.

Core Features & Use Cases

  • Phase-driven analysis: guides users through setup, data collection, and structured review to produce actionable insights.
  • Mode-aware workflow: supports interactive retro sessions and pipeline-based workflows for headless environments.
  • Post-mortem reporting: compiles findings and pointers for improvement to share with teams.

Quick Start

Start a retrospective for the current work session by initiating the Retro flow in your workflow environment.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I run a structured retrospective to identify improvement opportunities from recent work sessions?

A structured retrospective guides you through phase-based setup, data collection, and review to identify successes, issues, and actionable improvements from recent work sessions.

Can I automate post-mortem reporting in a headless pipeline instead of manually reviewing sprints?

Yes, the retrospective workflow detects pipeline modes to automate post-mortem reporting and extract artifacts from transcripts and workflows in headless environments without interactive input.

Does this retrospective analysis support extracting evidence from transcripts and workflow artifacts?

Yes, retrospective analysis extracts evidence and surfaces patterns by compiling findings and pointers for improvement directly from transcripts and workflow artifacts.

What is the best way to conduct a post-incident review that surfaces patterns rather than relying on memory?

A phase-driven retrospective collects evidence and surfaces patterns from post-incident reviews, replacing ad-hoc reflections with structured, actionable insights for team improvement.

Can I use this structured retrospective for both individual project sessions and team sprint reviews?

Yes, the retrospective workflow is applicable to both individuals and teams reviewing sprint work, project sessions, or post-incident reviews across interactive conversations.

How does the mode detection work between interactive and pipeline retrospectives?

Mode detection differentiates interactive retro sessions, which guide users through phases, from pipeline-based workflows, which automate artifact extraction and reporting for headless environments.