From scrum-master
This skill should be used when the user asks about "sprint velocity", "burndown chart", "burnup chart", "cycle time", "scrum metrics", "sprint report", "team velocity", "lead time", "throughput", "sprint burndown", "cumulative flow", "CFD", "WIP limits", "escaped defects", "carry-over rate", "Monte Carlo forecast", "velocity forecast", "sprint goal achievement", "retrospective action completion", "flow metrics", "predictability", "velocity variance", or needs guidance on measuring, interpreting, reporting, or forecasting scrum team performance.
npx claudepluginhub shinhf/skills-ide-resources --plugin scrum-masterThis skill uses the workspace's default tool permissions.
Guide the selection, calculation, interpretation, and reporting of scrum metrics. Metrics serve as diagnostic tools for team health and process improvement -- never as performance targets. When asked about metrics, always clarify the user's intent (diagnosis, forecasting, or reporting) and work only from data the user provides.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.
Guide the selection, calculation, interpretation, and reporting of scrum metrics. Metrics serve as diagnostic tools for team health and process improvement -- never as performance targets. When asked about metrics, always clarify the user's intent (diagnosis, forecasting, or reporting) and work only from data the user provides.
This skill is tool-independent. All metrics are calculated from data the user provides directly (inline text, pasted tables, markdown files, CSV snippets, issue tracker exports, or referenced local files). Never assume a specific project management tool. If required data is missing, prompt the user for the minimum additional information needed.
What it measures: Amount of work completed per Sprint, expressed in story points (or other consistent unit).
Calculation: Sum of story points for all items meeting the Definition of Done at Sprint end.
Interpretation:
What it measures: Remaining work in the Sprint Backlog over time.
Interpretation:
What it measures: Elapsed time from when work begins on an item to when it meets the Definition of Done.
Calculation: Done Date - Start Date (in working days).
Interpretation:
What it measures: Elapsed time from when an item enters the Product Backlog to when it is Done.
Interpretation:
What it measures: Number of items completed per time period (typically per Sprint).
Interpretation:
What it measures: Percentage of planned Sprint Backlog items not completed by Sprint end.
Calculation: (Items Not Done / Items Planned) x 100.
Interpretation:
What it measures: Defects found after the Increment is released (not caught by the team's DoD).
Interpretation: Rising escaped defects suggest the Definition of Done needs strengthening or test coverage is insufficient.
What it measures: Percentage of retro action items completed by their target date.
Interpretation:
What it measures: Subjective team satisfaction, typically collected via anonymous survey.
Interpretation: Treat as a leading indicator. Declining morale often precedes declining velocity and quality. Act before the lag metrics move.
When generating a sprint report, structure it as follows:
# Sprint [Number] Report
## Sprint Goal
[State the Sprint Goal and whether it was achieved]
## Key Metrics
| Metric | This Sprint | Previous Sprint | 3-Sprint Average |
|--------|-------------|-----------------|------------------|
| Velocity | [X] pts | [Y] pts | [Z] pts |
| Throughput | [X] items | [Y] items | [Z] items |
| Carry-over rate | [X]% | [Y]% | [Z]% |
| Cycle time (avg) | [X] days | [Y] days | [Z] days |
## Completed Items
[List of completed items with story points]
## Carried Over
[List of incomplete items with reason]
## Key Observations
[2-3 bullet points on trends, risks, or achievements]
## Improvement Actions
[Actions from retrospective]
Open the reference file when deeper detail is needed:
references/metrics-guide.md -- Open when the user needs: calculation walkthroughs with worked examples, burndown/burnup pattern diagnosis, cumulative flow diagram (CFD) reading, benchmark heuristics, multi-Sprint trend reports, stakeholder dashboards, or Monte Carlo forecasting steps