retro

Run a weekly engineering retrospective by invoking the skill with the trigger "weekly retro" and pointing it to your project's retros directory to load prior entries. This surfaces past learnings and milestones to inform your current sprint review.

Analyze project blockers and velocity trends by reviewing persistent retrospective files and timeline events. The skill surfaces patterns in blockers, velocity, and improvement opportunities across past sprints to guide actionable team discussions.

Pattern analysis for engineering learnings works by operating across per-project retros files and timeline events to identify recurring trends. It surfaces prior entries and recent milestones to provide context for current sprint reviews and future planning.

Yes, you can generate actionable outcomes after each sprint. The skill produces concrete improvements and follow-ups within your workspace, using persistent context from prior retros to guide actionable discussions for future planning.

You need a retros directory containing markdown files, typically structured as retros/*.md. The skill operates across these per-project retrospective files to locate prior entries, learnings, and milestones for context.

Avoid automated retrospective tools when your team lacks consistent markdown documentation or timeline event tracking. The skill requires persistent historical context across retros files to accurately surface patterns in velocity and blockers for future planning.