speckit-retrospective-analyze

Post-implementation retrospective analysis measures spec adherence by comparing completed work against spec.md, plan.md, and tasks.md. It evaluates requirement fidelity, architecture deviations, and task completion rates to identify where drift happened and what lessons to carry forward.

Spec adherence analysis in the SDD cycle is a post-implementation evaluation that quantifies requirement coverage from spec.md, plan.md, and tasks.md. It classifies items as implemented, partial, modified, or unspecified to evaluate fidelity and generate learning reports.

Run retrospective analysis after finishing the implementation to generate a retrospective report. The process applies completion-rate gating and evidence-backed reporting to produce a retrospective.md file saved to the FEATURE_DIR, summarizing spec adherence and prioritized recommendations.

Yes, retrospective analysis requires prerequisite validation before checking spec compliance. It validates the environment, applies completion-rate gating, and requires explicit user confirmation before modifying spec.md to prevent unintended spec changes during the review.

Constitution violations are detected during spec drift analysis and automatically treated as CRITICAL findings. Constitution compliance checks run alongside deviation severity classification, which labels findings as CRITICAL, SIGNIFICANT, MINOR, or POSITIVE to prioritize follow-up work.