retro

Facilitate team retrospectives to identify skill gaps and process inefficiencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rules, workspace, architecture-design, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams identify and address skill gaps, improve project processes, and enhance collaboration through automated retrospectives.

Core Features & Use Cases

  • Conversational Retrospectives: Initiate a retrospective with natural language commands like "retro" or "what went wrong".
  • Skill Gap Identification: Automatically detect and categorize issues such as false completions, skill not loaded, and playbook misses.
  • Root Cause Analysis: Analyze the reasons behind each issue, including missing guardrails, outdated playbooks, or architectural bottlenecks.
  • Skill Improvement: Recommend and implement improvements, including updating skills, adding guardrails, and refining playbooks.

Quick Start

To start a retro, simply say "retro" and follow the prompts to analyze your work session.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate team retrospectives to identify skill gaps and process inefficiencies?

Automated retrospectives analyze work sessions to detect skill gaps and process inefficiencies. The system categorizes issues like false completions and playbook misses, then recommends targeted improvements for team collaboration and project management.

What is root cause analysis for project management issues like false completions or playbook misses?

Root cause analysis investigates why project issues occur by examining missing guardrails, outdated playbooks, or architectural bottlenecks. This process identifies the underlying reasons behind false completions and skill gaps to drive process optimization.

How do I start a conversational retrospective for my software development workflow?

Start a conversational retrospective by typing natural language commands like "retro" or "what went wrong". Follow the prompts to analyze your software development work session and receive AI-driven recommendations for skill and process improvements.

Can I use automated retrospectives to update playbooks and add guardrails for my team?

Yes, automated retrospectives recommend and implement skill improvements by updating playbooks and adding guardrails. This addresses detected architectural bottlenecks and skill not loaded scenarios to enhance project efficiency.

Do I need specific workspace or architecture design rules configured before running a retrospective?

Yes, retrospectives require workspace, architecture-design, and rules dependencies to function correctly. These components provide the necessary context for analyzing process inefficiencies and generating accurate skill improvement recommendations.

Why does my team need AI-driven analysis for project process optimization instead of manual reviews?

AI-driven analysis detects process inefficiencies and skill gaps automatically during retrospectives, surpassing manual reviews. It provides automated recommendations for updating skills and refining playbooks to enhance team collaboration and project efficiency.