speckit-retrospective

Record completed Spec Kit workflows into feature-local retrospective artifacts before commit.

95|39|Updated Dec 15, 2025

Search Tags:#workflow #commit #retrospective #evidence #speckit #lessons #acceptance

Ready to run

npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-retrospective
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-retrospective
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a finished Spec Kit delivery into a durable, reviewable retrospective so the team does not lose acceptance evidence, workflow context, or useful lessons before commit.

Core Features & Use Cases

Workflow Traceability: Records the key user inputs, AI actions, validation evidence, and final state of a completed Spec Kit run.
Evidence Preservation: Summarizes validation results and points to the artifacts needed for later review or rubric scoring.
Lesson Capture: Creates pending improvement candidates only when there is a reusable, evidence-backed process lesson worth keeping.
Use Case: After a feature has been accepted, use this Skill to write the retrospective artifacts, update workflow state, and decide whether the next step is commit or lesson promotion.

Quick Start

Ask the skill to record the completed Spec Kit workflow into the feature-local retrospective files before commit.

Frequently Asked Questions about speckit-retrospective

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

FAQPage Schema

How do I record a completed Spec Kit workflow into a retrospective before commit?▼

To record a completed Spec Kit workflow before commit, generate retrospective artifacts by updating feature-local files like workflow-record.md, improvement-candidates.md, and workflow-state.json to preserve validation evidence and workflow context.

Why do I lose acceptance evidence and workflow context after a Spec Kit delivery?▼

Acceptance evidence and workflow context are lost after a Spec Kit delivery without a retrospective process that captures validation results and final workflow state into durable files before committing the code.

How do I capture reusable workflow lessons from a finished feature delivery?▼

Capture reusable workflow lessons by creating pending improvement candidates only when there is an evidence-backed process lesson worth keeping, writing these entries into the feature-local improvement-candidates.md file.

What files need to be updated to maintain workflow traceability for Spec Kit projects?▼

Maintaining workflow traceability for Spec Kit projects requires updating workflow-record.md for inputs and actions, improvement-candidates.md for lessons, workflow-state.json for final state, and review navigation links.

Does this retrospective workflow apply before or after feature acceptance?▼

This retrospective workflow applies specifically to post-acceptance delivery on Spec Kit projects that need workflow traceability, evidence capture, and lesson review, ensuring constraints and acceptance evidence are preserved.

When should I not use a retrospective artifact generation workflow for Spec Kit?▼

Retrospective artifact generation for Spec Kit should not be used when a feature has not reached post-acceptance delivery, as it requires completed validation evidence and a final workflow state to record accurately.