Sprint Review.prompt
--- name: sprint-review description: "End-of-sprint summary across all repos -- completed items, carryover, velocity trends, blockers, team contributions, and retrospective insights" agent: analytics tools: - github/* - createFile - createDirectory - ask_questions --- Generate an end-of-sprint review summary with completed work, carryover items, velocity metrics, and team contributions. Save both markdown and HTML versions. ${input:details:Optional: sprint/milestone name, date range, repo, or 'org:orgname'} ## Steps 1. Get the authenticated user with #tool:mcp_github_github_get_me. 2. Load repo scope from `.github/agents/preferences.md` if present. By default, aggregate across ALL accessible repos. 3. Identify the sprint scope: - If a milestone is specified, use it as the sprint boundary - If a date range is given, use those dates - Default: last 2 weeks 3. Collect sprint data: - **Completed:** Issues closed and PRs merged during the sprint - **Carryover:** Issues/PRs that were in the sprint but not completed - **New work:** Items added mid-sprint - **Blockers:** Items that were blocked or stuck 4. Calculate velocity metrics: - Items completed vs. planned - Story points (if labels indicate points) - Comparison to previous sprint - Cycle time distribution 5. Collect team contributions: - Items completed per team member - Reviews done per team member - Highlights and notable contributions 6. Generate BOTH documents: - Markdown: `.github/reviews/analytics/sprint-review-{date}.md` - HTML: `.github/reviews/analytics/sprint-review-{date}.html` With sections: Sprint Summary, Completed Work, Carryover Items, Velocity Metrics, Team Contributions, Blockers & Risks, Retrospective Prompts 7. Include retrospective prompts: - What went well this sprint? - What could be improved? - What should we start/stop/continue? - Any recurring blockers to address? After the review: _"Want to plan the next sprint? Or dive into any specific area?"_
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{date}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo accesswatch/agent-forge (MIT). A "Sprint Review.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
accesswatch/agent-forge · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar