speckit-retrospective-analyze

To measure spec adherence after a build, you can analyze completed implementations against spec artifacts like spec.md, plan.md, and tasks.md. This generates a retrospective report containing adherence metrics and actionable recommendations for future cycles.

Spec drift occurs when a finished implementation diverges from its original specification. You detect it by running a post-implementation review that evaluates your codebase against spec.md, plan.md, and tasks.md to identify discrepancies and output a retrospective report.

You check constitution compliance by analyzing completed implementations against your project's governance artifacts. This evaluates whether the build adheres to defined quality guidelines and outputs actionable recommendations within a retrospective.md report.

Yes, you can generate a retrospective report by analyzing a finished project against existing spec.md, plan.md, and tasks.md files. The output is a retrospective.md document containing an executive summary, adherence metrics, and actionable recommendations.

You should run a post-implementation spec review after a project build is completed to expose spec drift. It evaluates your implementation against spec artifacts to extract key learnings and provide actionable recommendations for future SDLC cycles.

The best way to extract learnings is to analyze the completed implementation against spec.md, plan.md, and tasks.md. This measures adherence, detects drift, and produces a retrospective.md report with an executive summary and actionable recommendations for future cycles.