cnoe-io/sprint-progress-report
charts/ai-platform-engineering/data/skills/sprint-progress-report/SKILL.md
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
$ install --global
skillsauthnpx skillsauth add cnoe-io/ai-platform-engineering sprint-progress-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:51 PM4.2s2 files scanned
SKILL.md
- name:
- sprint-progress-report
- description:
- Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
Sprint Progress Report
Query Jira to build a detailed sprint progress report including velocity, burndown, completion rates, and blockers.
Instructions
Phase 1: Sprint Data Collection (Jira Agent)
- Identify the current sprint:
- Get the active sprint from the team's Jira board
- Collect sprint name, start date, end date, and goal
- Fetch all sprint issues:
- Stories, tasks, bugs, and subtasks in the sprint
- For each: key, summary, status, assignee, story points, priority, labels
- Fetch sprint history (for velocity):
- Last 3-5 completed sprints
- Committed vs. completed story points per sprint
Phase 2: Metrics Calculation
- Burndown Metrics:
- Total committed story points
- Completed story points
- Remaining story points
- Percentage complete
- Days remaining in sprint
- Projected completion (on track / at risk / behind)
- Velocity:
- Average velocity over last 3-5 sprints
- Current sprint pace vs. average
- Velocity trend (increasing, stable, decreasing)
- Issue Distribution:
- By status (To Do, In Progress, In Review, Done)
- By type (Story, Bug, Task)
- By assignee (workload balance)
- By priority (Critical, High, Medium, Low)
Phase 3: Blocker & Risk Analysis
- Identify blockers:
- Issues with `blocked` status or `blocker` label
- Issues with no activity for >2 days while In Progress
- Issues with unresolved dependencies
- Identify risks:
- High-priority items still in To Do with <3 days remaining
- Unassigned items
- Items added mid-sprint (scope creep)
- Items removed from sprint (scope reduction)
Output Format
```markdown
Sprint Progress Report
Sprint: Sprint 24 - "Platform Reliability" Period: Feb 3 - Feb 14, 2026 | Days Remaining: 5 Sprint Goal: Improve platform monitoring and reduce incident response time
Summary
| Metric | Value | |--------|-------| | Committed | 34 story points (15 issues) | | Completed | 21 story points (9 issues) | | Remaining | 13 story points (6 issues) | | Completion | 62% | | Projection | On Track (avg velocity: 32 pts) | ```
Examples
- "Generate a sprint progress report for the current sprint"
- "Show me sprint velocity and burndown"
- "Are we on track to complete this sprint?"
- "What are the blockers in the current sprint?"
- "Show team workload distribution for this sprint"
Guidelines
- Always calculate projected completion based on historical velocity, not optimistic estimates
- Flag sprints as "at risk" if completion rate is below 80% at the midpoint
- Highlight scope changes (issues added or removed mid-sprint) separately
- If story points are not used, fall back to issue count
- Keep the report scannable - lead with the summary, details below
- Include the sprint goal prominently so progress can be evaluated against intent
Related Skills
cnoe-io/streaming-testing
testing
VerifiedTrustedCommunity
Compare A2A streaming behaviour across supervisor versions. Captures SSE events, analyzes metadata flags (is_narration, is_final_answer), and produces side-by-side comparison reports.
345SKILL.mdUpdated Apr 15, 2026
cnoe-io/security-vulnerability-report
development
VerifiedTrustedCommunity
Scan GitHub repositories for security vulnerabilities including Dependabot alerts, code scanning results, and secret scanning findings. Use when auditing repository security, preparing compliance reports, or triaging vulnerability alerts.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/review-specific-pr
development
VerifiedTrustedCommunity
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/review-open-pull-requests
testing
VerifiedTrustedCommunity
List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.
345SKILL.mdUpdated Apr 4, 2026