Generate a data-driven delivery forecast based on current velocity and remaining backlog — giving stakeholders a realistic, honest view of when things will be done.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-metrics-reporting:forecast-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a data-driven delivery forecast based on current velocity and remaining backlog — giving stakeholders a realistic, honest view of when things will be done.
Generate a data-driven delivery forecast based on current velocity and remaining backlog — giving stakeholders a realistic, honest view of when things will be done.
Formula: Sprints Remaining = Remaining SP / Velocity
| Scenario | Velocity | Sprints Remaining | Forecast Date |
|---|---|---|---|
| Optimistic | Max velocity (45 SP) | X | [date] |
| Realistic | Average velocity (36 SP) | X | [date] |
| Conservative | 80% of average (29 SP) | X | [date] |
"Based on our last 6 sprints averaging 36 story points, and with 180 story points remaining, our realistic forecast is 5 sprints — a target date of [date]. Under conservative assumptions (accounting for risk and uncertainty), we would complete by [date+2 weeks]."
| Committed Date | Realistic Forecast | Gap | |
|---|---|---|---|
| Release date | [date] | [forecast date] | [+/- days] |
If gap exists, flag it and recommend scope cut or date negotiation.
Options to explore:
/cut-scope or /status-updatenpx claudepluginhub devmuslim/pdm-skills --plugin pdm-metrics-reportingCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.