qa-retro

Facilitate structured QA retrospective meetings to identify bottlenecks and generate action items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Quality Assurance professionals conduct effective retrospectives to identify areas for improvement in their processes and workflows.

Core Features & Use Cases

  • Facilitate Retrospective Meetings: Guide teams through structured retrospective sessions.
  • Identify Bottlenecks: Help pinpoint issues hindering QA efficiency and effectiveness.
  • Action Item Generation: Assist in creating actionable steps to address identified problems.
  • Use Case: A QA team is consistently facing delays in test execution. This Skill can be used to run a retrospective to understand the root causes and define steps to improve the testing pipeline.

Quick Start

Use the qa-retro skill to start a retrospective for the last sprint.

Frequently Asked Questions about qa-retro

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

FAQPage Schema
How do I run a QA retrospective for an agile sprint?

A QA retrospective is a structured meeting to review a completed sprint and identify process bottlenecks. This skill facilitates the session to pinpoint issues hindering QA efficiency and generate actionable improvement items for the team.

What is the best way to identify bottlenecks in our testing pipeline?

The best way to identify bottlenecks is to conduct a structured QA retrospective. This process helps analyze recent sprint delays, understand root causes affecting test execution, and define actionable steps to improve testing workflows.

How do I generate actionable improvement items from a quality assurance retrospective?

Generating actionable items involves guiding the QA team through a structured retrospective to address identified problems. The process translates bottlenecks found during sprint review into concrete steps for enhancing QA efficiency.

Can I use this approach for a QA team facing consistent delays in test execution?

Yes, you can use this retrospective approach for a QA team facing delays in test execution. It is designed to help understand root causes of testing pipeline issues and define steps to improve overall QA effectiveness.

Do I need a completed sprint to review QA processes?

Yes, you need a defined sprint or iteration for review to effectively use this retrospective process. Analyzing a completed development cycle is required to identify bottlenecks and generate relevant process improvement items.