Pm Skills
Routes project-delivery requests to the right capability — sprint analytics, portfolio health, issue-tracker queries, documentation, tracker administration.
Before & after
Same prompt, same agent — the only difference is the skill.
Sprints taking longer than expected is a common challenge, especially as teams scale. There are usually a few things going on — either estimates are too optimistic, scope creeps mid-sprint, blockers aren't being surfaced early, or the team is overloaded. To dig into what's happening in your case, I'd need to know more. How many sprints are we talking about? Is it consistent overrun, or just a recent thing? Do you track velocity metrics — points planned vs. completed? Are there particular types of work that tend to slip, or is it across the board? Also, how big is your team? Is this a new team, or an established one? Do you use Jira or another tracking tool where I could see the actual data? Once I understand the pattern, I can help you identify the root cause and suggest fixes. Is it estimation accuracy, planning discipline, technical debt slowing things down, or team capacity issues?
SPRINT HEALTH ANALYSIS & OPTIMIZATION PLAN CURRENT STATE (Last 8 sprints) Planned velocity: 120 points/sprint Actual completion: 78 points/sprint (65% delivery rate) Slippage: 42 points avg per sprint (scope creep) Burn-down curve: Days 1-5 on track, Days 6-10 plateau (daily standup shows low progress) VELOCITY TREND • Sprint 1: 110 pts (91%) • Sprint 2: 82 pts (68%) • Sprint 3: 72 pts (60%) • Sprint 4-8: avg 78 pts (65%) TREND: Declining velocity, hitting floor around 65-70% ROOT CAUSE ANALYSIS 1. ESTIMATION BIAS (40% of overrun) • 8-point stories avg 12-14 days (under-estimated by 40%) • Team members new; ramp-up costs not factored • Complex edge cases discovered mid-sprint 2. SCOPE CREEP (35% of overrun) • Unplanned bugs: 2-3 per sprint (avg 8 hours each) • Urgent asks from leadership mid-sprint: ~1 per sprint • Refactoring sneaks in (1-2 stories) 3. BLOCKERS (25% of overrun) • Waiting on design review: 2-3 days avg • API changes from backend team: 1-2 day delays • Merge conflicts / CI failures: 1 day overhead RECOMMENDED ACTIONS (Priority order) 1. Estimation calibration (implement immediately) • Use t-shirt sizing (S/M/L) + historical velocity chart • 5-point story = 5 ideal days + 1 day buffer for unknowns • Max story size: 8 points (anything bigger → spike first) • Retrospective: post-sprint story accuracy review 2. Scope gate (starts next sprint) • No mid-sprint requests without sprint closure review • Urgent asks: follow interrupt protocol (trade with planned work) • Separate bug backlog (reserve 10% capacity) 3. Dependency mapping (within 2 weeks) • Identify design, backend, infra dependencies • Prep those items one sprint ahead • Daily standup: surface blockers by noon EXPECTED OUTCOME Sprint velocity: 100+ points (83%+ delivery) within 3 sprints. First improvements visible in Sprint 1 with estimation fixes alone.
About this skill
name: pm-skills description: Use when Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analy...
Pm Skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a full goal→plan→execute→verify→close delivery loop through the repo-wide agent-harness with Jira MCP data bridged into the domain's analytics tools. Distinct from product-team (what to build vs how to deliver it), business-operations (internal ops), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the pm-skills skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Pm Skills; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: pm-skills
description: Use this skill when coordinating project-delivery work that spans multiple project-management disciplines and the right sub-skill needs to be selected.
version: 1.0.0
category: Business & Ops / Project Management
author: AgentVolt
license: proprietary
tags:
- business-ops
- project-management
---
# Pm Skills
Routes project-delivery requests to the right capability — sprint analytics, portfolio health, issue-tracker queries, documentation, tracker administration, or team communications — and can drive a full goal-to-close delivery loop when a request spans more than one.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Meeting Analyzer
Analyzes meeting transcripts and recordings to surface behavioral patterns, communication anti-patterns, and actionable coaching feedback.
Atlassian Templates
Creates and maintains Jira and Confluence templates, blueprints, and reusable content structures so teams stop rebuilding the same document or issue layout by hand.
Confluence Expert
Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation.
Jira Expert
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features.