speckit-retrospective-analyze

Analyze completed implementations against specification documents to measure adherence and drift.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-retrospective-analyze-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-retrospective-analyze
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-retrospective-analyze
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-retrospective-analyze-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams review a finished implementation against its specification, plan, and task list so they can quantify drift, spot missed requirements, and capture lessons for future work.

Core Features & Use Cases

  • Spec Adherence Analysis: Compare the implementation to spec.md, plan.md, and tasks.md to identify what was implemented, modified, partially done, or omitted.
  • Drift and Risk Review: Detect architecture changes, task mismatches, constitution issues, and other deviations that could affect quality or delivery.
  • Actionable Retrospectives: Produce a concise retrospective report with findings, severity levels, proposed spec changes, and follow-up recommendations.

Quick Start

Ask this Skill to analyze the completed feature and generate a retrospective report from the project’s spec, plan, and task files.

Frequently Asked Questions about speckit-retrospective-analyze

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

FAQPage Schema
How do I measure spec drift after a feature implementation?

You measure spec drift by comparing completed implementations against specification documents, plans, and task lists to identify deviations, missed requirements, and task mismatches affecting delivery quality.

What is a post-implementation retrospective for software projects?

A post-implementation retrospective analyzes completed implementations against specifications to quantify drift, review architecture changes and blockers, and capture actionable lessons for future work.

How do I check requirement coverage and constitution compliance?

You check requirement coverage and constitution compliance by auditing completed implementations against specification documents to classify severity levels and identify missed or modified requirements.

Can I generate an actionable retrospective report from spec files?

Yes, you can generate a concise retrospective report from spec, plan, and task files that includes findings, severity levels, proposed spec changes, and follow-up recommendations for future work.

Does this approach require spec, plan, and task list files to work?

Yes, this retrospective analysis requires spec-kit projects containing spec.md, plan.md, and tasks.md files to compare implementations and measure adherence, drift, and task completion accurately.

What is the best way to identify missed requirements in a completed implementation?

The best way to identify missed requirements is comparing the implementation to spec.md and tasks.md to detect what was partially done, omitted, or modified, then classifying severity levels for reporting.