retro

Analyzes observable signals to identify collaboration friction and suggest process refinements.

5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/suzbot/petri --skill retro-suzbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/suzbot/petri/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/suzbot/petri --skill retro-suzbot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and address friction points in collaboration, aiming to improve future interactions and reduce context overhead.

Core Features & Use Cases

  • Post-feature Reflection: Automatically runs after a feature is completed to assess the collaboration process.
  • Mid-session Check-in: Can be triggered by the user for an unscheduled process review.
  • Friction Identification: Analyzes observable signals like interrupted actions, clarification requests, and decision-making patterns.
  • Use Case: After a complex feature development cycle, this skill can be invoked to pinpoint where communication broke down or where clearer documentation could have saved time, leading to actionable improvements for the next cycle.

Quick Start

Ask the retro skill to perform a process check-in for the current session.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I identify collaboration friction after a complex feature development cycle?

A mid-session process check-in analyzes real-time collaboration friction by evaluating decision-making patterns and interrupted actions. Triggering this unscheduled reflection suggests high-leverage improvements to documents, skills, or agents to optimize your current workflow.

What is workflow optimization reflection and when should I use it?

Workflow optimization reflection is a process improvement technique that analyzes collaboration signals to propose refinements. You should use it after completing a feature or mid-session to reduce context overhead and address friction points in future interactions.

How do I run a process check-in to analyze decision-making patterns?

You can run a process check-in by requesting a mid-session reflection to analyze observable decision-making patterns and clarification requests. This generates high-confidence, actionable suggestions for refining documents, skills, or agents.

Can I use retrospective analysis for mid-session process improvement?

Yes, you can trigger retrospective analysis for an unscheduled mid-session process review. It evaluates collaboration friction and decision-making patterns to propose immediate, high-leverage improvements to your current workflow and reduce context overhead.

What are the limitations of analyzing observable signals for process improvement?

Analyzing observable signals like interrupted actions is limited to identifying collaboration friction within the current session context. It focuses on proposing process refinements and does not automatically fix broken documentation or external communication channels.