sprint — Claude Code command: plan sprints, run retros
Three modes for sprint lifecycle: plan sprints with capacity estimates and task selection, run retrospectives with structured feedback, generate release notes from technical artifacts.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skillsWhat sprint does
The /sprint command guides you through the complete sprint cycle. In plan mode, it calculates available team hours after meetings, PTO and on-call rotations, recommends which stories fit the capacity, flags dependencies and risks. In retro mode, it takes team feedback and structures it by one of three formats: Start/Stop/Continue, 4Ls, or Sailboat — identifies themes and patterns, produces action items. Release notes mode converts tickets and PRs into user-facing copy: translates technical details into customer benefits, groups changes by type (New Features, Improvements, Bug Fixes), and offers formats for blog, email or Slack.
Each mode generates a ready-to-use template with tables and checklists. The command reserves a 20% capacity buffer for unplanned work because teams that plan at full capacity consistently miss their commitments. For retros, it focuses on 2–3 high-impact actions teams will actually do, rather than a list of ten ideas nobody revisits.
What it helps with
- estimate team capacity for a sprint accounting for time off and meetings
- select stories for a sprint knowing dependencies and risks
- structure team feedback after a sprint into concrete action items
- write release notes that make sense to users, not engineers
Example prompts for the agent
- /sprint plan 2-week sprint, 4 engineers, checkout improvements focus
- /sprint retro [paste team feedback from our retrospective survey]
- /sprint release-notes [paste merged PRs and ticket list for this release]
How to install sprint
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-execution@pm-skills2Manually: put the files in place
.claude/commands/sprint.mdCall it with /sprint. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/sprint.mdCall it with /prompts:sprint. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/sprint.prompt.mdManually: put the files in place
.gemini/commands/sprint.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about sprint
How do I install sprint in Claude Code?
Run these commands in order: /plugin marketplace add phuryn/pm-skills, /plugin install pm-execution@pm-skills, then copy .claude/commands/sprint.md to your project's commands folder.
What does the sprint command do?
It covers three sprint phases: plan prepares sprint planning with capacity math and story selection, retro structures team feedback into action items using a chosen format, release-notes transforms tickets and PRs into a release announcement.
Why reserve a 20% capacity buffer?
Sprints planned at 100% capacity almost always slip because unplanned work always appears. A 20% buffer makes it realistic that your team completes what it commits to.
Source text
sprint.md · MIT
--- description: Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes argument-hint: "[plan|retro|release-notes] <context>" --- # /sprint -- Sprint Lifecycle Three modes covering the sprint lifecycle: **plan** for sprint planning, **retro** for retrospectives, **release-notes** for shipping communication. ## Invocation ``` /sprint plan 2-week sprint, 4 engineers, focus on checkout improvements /sprint retro [paste team feedback or sprint data] /sprint release-notes [paste tickets, changelog, or PRD] /sprint # asks which phase you're in ``` ## Modes --- ### Plan Mode Prepare for sprint planning with capacity estimation, story selection, and risk identification. #### Workflow **Step 1: Gather Sprint Context** - Sprint duration (1 or 2 weeks) - Team composition (engineers, designers, QA — and availability) - Sprint goal or focus area - Backlog items to consider (paste, upload, or describe) - Any carry-over from last sprint - Known interruptions (holidays, on-call, meetings) **Step 2: Estimate Capacity** Apply the **sprint-plan** skill: - Calculate available engineering hours/points after meetings, on-call, PTO - Apply a velocity adjustment based on historical data (if provided) or industry standard (70% of theoretical capacity) - Show capacity breakdown per team member **Step 3: Select and Sequence Stories** - Recommend which stories fit within capacity - Flag dependency chains (A must complete before B starts) - Identify risks: stories that are underspecified, have external dependencies, or need design input - Balance quick wins with larger items - Ensure every story has acceptance criteria **Step 4: Generate Sprint Plan** ``` ## Sprint Plan: [Sprint Name/Number] **Duration**: [dates] **Sprint Goal**: [one sentence] **Team**: [members and availability] ### Capacity | Member | Available Days | Points/Hours | Notes | |--------|--------------|-------------|-------| **Total capacity**: [X] points/hours **Recommended commitment**: [Y] points/hours (with buffer) ### Selected Stories | # | Story | Points | Owner | Dependencies | Risk | |---|-------|--------|-------|-------------|------| ### Sprint Risks 1. [Risk] — Mitigation: [action] ### Definition of Done - [ ] Code reviewed - [ ] Tests passing - [ ] Deployed to staging - [ ] QA approved - [ ] Documentation updated (if applicable) ``` --- ### Retro Mode Facilitate a structured retrospective that produces actionable improvements. #### Workflow **Step 1: Gather Sprint Feedback** Accept input as: - Team feedback (pasted from a survey, Slack, or collaborative doc) - Sprint metrics (velocity, bugs, incidents) - The user's own observations Ask: "Which retro format do you prefer?" - **Start/Stop/Continue** (simple, fast) - **4Ls** (Liked, Learned, Lacked, Longed for) - **Sailboat** (Wind = helps, Anchor = slows, Rocks = risks, Island = goals) **Step 2: Analyze and Structure** Apply the **retro** skill: - Categorize feedback into the chosen framework - Identify themes and patterns - Separate symptoms from root causes - Highlight wins worth celebrating **Step 3: Generate Retro Summary** ``` ## Sprint Retrospective: [Sprint Name] **Date**: [today] **Format**: [Start/Stop/Continue | 4Ls | Sailboat] **Participants**: [if known] ### What Went Well [Grouped themes with supporting evidence] ### What Didn't Go Well [Grouped themes with root cause analysis] ### Key Insights [2-3 patterns that emerged] ### Action Items | # | Action | Owner | Deadline | Priority | |---|--------|-------|----------|----------| ### Metrics This Sprint | Metric | This Sprint | Last Sprint | Trend | |--------|-----------|------------|-------| ``` --- ### Release Notes Mode Generate user-facing release notes from technical artifacts. #### Workflow **Step 1: Accept Release Content** Accept: - Jira/Linear tickets or changelog - PRD or feature specs - Git commit messages or PR descriptions - Team's internal summary of what shipped **Step 2: Transform** Apply the **release-notes** skill: - Translate technical language into user benefits - Categorize as: New Features, Improvements, Bug Fixes - Write in the product's voice (ask about tone if not clear) - Highlight the most impactful change first **Step 3: Generate Release Notes** ``` ## What's New — [Version/Date] ### Highlights [1-2 sentence summary of the most important change] ### New Features - **[Feature Name]** — [user-facing benefit in plain language] ### Improvements - **[Improvement]** — [what's better now] ### Bug Fixes - Fixed [issue] that caused [user impact] ### Coming Soon [Optional teaser for next release] ``` Save as markdown and offer to format for different channels (blog post, in-app, email, Slack announcement). ## Notes - For plan mode: protect 20% buffer for unplanned work — teams that plan at 100% capacity always miss - For retro mode: focus on 2-3 high-impact action items, not 10 things nobody will do - For release notes: always frame changes as user benefits, not technical implementations - Each mode can chain to the others: plan → (sprint happens) → retro → release-notes
© Paweł Huryn · MIT · phuryn/pm-skills