sprint-report

Generate a weekly sprint report by asking the skill to summarize merged PRs, in-progress work, blockers, and completed issues across all project repositories. It produces a structured summary with velocity metrics suitable for stakeholder updates.

A team velocity summary includes shipped work from merged PRs, in-progress tasks, current blockers, and completed issues. It also calculates velocity metrics like PRs merged, issues closed, and average cycle time to track weekly progress.

Yes, you can aggregate merged PRs and blockers across multiple repositories. The skill applies across all repositories in the project to compile a comprehensive sprint-wide report for leads and stakeholders.

Sprint reporting works for stakeholder updates and leadership reviews by producing a concise, structured output. It collects shipped work, in-progress items, blockers, and velocity metrics to keep teams aligned during standups or leadership reviews.

The best way to track team blockers and in-progress work is to compile a weekly sprint summary that aggregates current blockers and ongoing tasks alongside shipped PRs and velocity metrics, providing a clear overview for team leads.