retrospective-workflow

Automate post-story retrospectives and generate handoffs for the Agent Package Manager.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/vineethsoma/agent-packages --skill retrospective-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective-workflow
Source: https://github.com/vineethsoma/agent-packages/tree/main/skills/retrospective-workflow
Command: npx skills add https://github.com/vineethsoma/agent-packages --skill retrospective-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Retrospectives after story completion are often ad-hoc, causing missed learnings and inconsistent handoffs. This skill provides a repeatable process with templates, metrics tracking, and a generated handoff protocol to ensure continuous improvement and clear collaboration with the Agent Package Manager.

Core Features & Use Cases

  • Templates for retro process, metrics tracking, and handoff spec generation
  • Scripts to initialize retrospectives, gather metrics, and validate outputs
  • Prompts to facilitate retrospective input and YAML handoff generation
  • Use Case: After finishing a story, run the retrospective to collect data, consolidate learnings, and produce a handoff for downstream actions.

Quick Start

Follow these steps to initialize and run a retrospective workflow for a completed story, then generate a handoff for Agent Package Manager.

Frequently Asked Questions about retrospective-workflow

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

FAQPage Schema
How do I automate post-merge story retrospectives?

You can automate post-merge story retrospectives by running scripts to initialize the process, collect feedback, and generate a structured handoff for the Agent Package Manager. This workflow applies after story merges within the speckit structure.

What is an Agent Package Manager handoff and when do I need it?

An Agent Package Manager handoff is a generated YAML output consolidating retrospective metrics and learnings. You need it after story completion to trigger downstream actions and ensure continuous improvement across your features.

How do I track metrics during a sprint retrospective?

You track metrics during a sprint retrospective by applying template-driven scripts that gather data and validate outputs. The workflow initializes within the specs directory structure to ensure complete and verifiable metric collection.

Does this retrospective workflow work with the speckit directory structure?

Yes, the retrospective workflow applies directly after story merges in the speckit structure. It operates across the specs/{feature}/stories/{story-id}/retro directory paths to manage feedback and generate handoffs.

What is the best way to generate a YAML handoff for continuous improvement?

The best way to generate a YAML handoff is using template-driven prompts that facilitate retrospective input. These prompts consolidate feedback and metrics into a structured format for the Agent Package Manager.

Why are my ad-hoc retrospective learnings being missed?

Ad-hoc retrospective learnings are missed due to a lack of repeatable processes and validation steps. Implementing template-driven scripts ensures feedback consolidation and generates actionable handoffs to prevent lost data.