groove-utilities-memory-retrospective

To analyze workflow trends, this Skill reviews your session ratings, recurring mistakes, and captured learnings over a specified period. It generates a retrospective report summarizing your performance and highlighting areas for improvement.

Running a weekly workflow retrospective requires access to your memory logs, task backend, and git history. This Skill processes these inputs to review activity volume and identify mistake patterns from the past week.

Yes, you can generate a retrospective report for a week, a month, or all time. The Skill analyzes your workflow trends and incident tracking data over the specified period to provide a concise overview of workflow health.

Yes, you need git history for activity volume and a task backend for incident tracking to review workflow learnings. Memory logs are also required to capture session ratings and summarize recurring mistakes for trend analysis.

Reflection on past performance helps with workflow optimization by identifying recurring issues and highlighting key learnings. This Skill analyzes session ratings and mistake patterns to provide insights into your productivity trends.

Incomplete workflow trends in retrospective analysis occur when memory logs, task backend, or git history data is missing. The Skill requires all three inputs to accurately review session ratings and calculate activity volume.