17-retrospective

Conduct structured project retrospectives through guided interview questions and action planning.

1|Updated May 31, 2026
One-click install
npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 17-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 17-retrospective
Source: https://github.com/joseph-c-mcguire/spec-driven/tree/main/.cursor/skills/17-retrospective
Command: npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 17-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of conducting comprehensive project retrospectives by providing a structured interview process, capturing insights, and generating an action plan.

Core Features & Use Cases

  • Structured Interviews: Guides users through a series of questions to identify what went well, what needs improvement, and potential process fixes.
  • Action Planning: Facilitates the creation of a prioritized action backlog for follow-up.
  • Use Case: After completing a project milestone or phase, use this Skill to review the process, gather feedback, and plan for future improvements.

Quick Start

Run the '17-retrospective' skill to initiate a project retrospective.

Frequently Asked Questions about 17-retrospective

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

FAQPage Schema
How do I conduct a structured project retrospective to gather user feedback?

A structured project retrospective uses guided interview prompts to gather user feedback on project performance, capturing insights on what went well and identifying areas for process improvement.

What is the best way to prioritize action items after a project milestone review?

The best way to prioritize action items after a project milestone review is to analyze conversation logs and pipeline skills, then use structured interviews to capture insights and generate a prioritized action backlog.

How do I create an action plan for process improvement from project reviews?

You can create a process improvement action plan by running a retrospective skill that guides you through targeted questions, analyzing project data, and facilitating the creation of a prioritized action backlog for follow-up.

When should I run a project retrospective for optimal action planning?

You should run a project retrospective after completing a project milestone or phase, allowing you to review the process, gather user feedback, and plan future improvements while insights are fresh.

Can I analyze conversation logs and pipeline skills during a retrospective?

Yes, a structured retrospective requires the analysis of conversation logs and pipeline skills alongside user interviews to accurately capture insights and prioritize action items for process fixes.

Does a structured project retrospective require prior dependencies or specific inputs?

A structured project retrospective requires no external dependencies, but you need accessible conversation logs and pipeline skill data to effectively analyze performance and generate a prioritized action backlog.