des-retrospective

To generate an evidence-grounded retrospective report, compare planned versus completed work using sprint plans and story catalogs. The system extracts blockers, root causes, and lessons learned, explicitly marking any evidence gaps before producing the final report.

Analyzing sprint blockers and CI/CD lessons involves tracing friction back to root causes during implementation cycle reviews. The process evaluates technical, quality, and governance outcomes to produce actionable improvement items rather than unstructured post-mortems.

When upstream implementation artifacts are incomplete, the retrospective process explicitly marks evidence gaps rather than fabricating results. It proceeds by comparing available sprint plan and workflow status data to generate a report with clearly documented missing inputs.

Yes, sprint retrospective outputs directly update workflow status files with explicit next-step decisions. The process recommends a subsequent support skill, such as correct-course, aligned with the retrospective outcome to drive continuous workflow iteration.

A retrospective report is needed for release readiness, demo, or handoff reviews when you must evaluate implementation cycle outcomes against the original plan. It captures technical and governance lessons to ensure smoother future deployments.

Yes, the retrospective workflow supports artifact quality and governance analysis by evaluating completed work against expected standards. It extracts specific governance lessons and quality issues to form concrete action items for the next sprint.