ops-retro

Facilitate structured retrospective meetings for DevOps and platform teams.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill ops-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-retro
Source: https://github.com/hilaryosborne/skills/tree/main/devops-platform/ops-retro
Command: npx skills add https://github.com/hilaryosborne/skills --skill ops-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in conducting effective retrospectives for DevOps and platform teams, facilitating learning and continuous improvement.

Core Features & Use Cases

  • Structured Retrospective Guidance: Provides a framework for running a retrospective meeting.
  • Action Item Generation: Helps in identifying and documenting actionable improvements.
  • Use Case: A platform team has just completed a challenging sprint involving a major incident. Use this Skill to guide the team through a retrospective to understand what went well, what could be improved, and to define concrete actions for the next sprint.

Quick Start

Use the ops-retro skill to facilitate a retrospective for the last sprint.

Frequently Asked Questions about ops-retro

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

FAQPage Schema
How do I conduct a retrospective for a DevOps platform team?▼

To conduct a retrospective for a DevOps platform team, use a structured framework to guide the meeting, analyze past performance, and document concrete actions for continuous improvement.

What is the best way to generate action items after a challenging sprint?▼

The best way to generate action items after a sprint is to use a retrospective framework that identifies what went well and what needs improvement, defining concrete actions for the next cycle.

Can I use a retrospective framework to analyze a major platform incident?▼

Yes, you can use a retrospective framework to analyze a major platform incident, guiding the team through a post-mortem to understand project dynamics and define future preventative actions.

How does agile continuous improvement work with iterative development cycles?▼

Agile continuous improvement works with iterative development cycles by analyzing past team performance during retrospectives and defining specific future actions to enhance project workflows.

Do I need specific tools to facilitate a structured retrospective meeting?▼

No specific tools are required, but you need a clear understanding of team dynamics and project post-mortems to effectively guide a structured retrospective meeting and generate actionable insights.