scrum-master-agent

Normalize sprint data from Linear, Jira, GitHub Projects, and Azure DevOps into a unified analytics model.

1|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Yona544/AIskils --skill scrum-master-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrum-master-agent
Source: https://github.com/Yona544/AIskils/tree/main/generated-skills/scrum-master-agent
Command: npx skills add https://github.com/Yona544/AIskils --skill scrum-master-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scrum Master Agent provides sprint analytics, backlog prioritization, capacity planning, and actionable insights with context-aware outputs.

Core Features & Use Cases

  • Sprint planning and capacity planning with velocity tracking
  • Backlog grooming with multi-factor prioritization
  • Sprint health monitoring, retrospectives, and risk alerts
  • Multi-tool adapters (Linear, Jira, GitHub Projects, Azure DevOps)
  • Token-efficient reporting for desktop and CLI

Quick Start

Sample invocation: @scrum-master-agent followed by sprint data and backlog in Linear or Jira formats

Frequently Asked Questions about scrum-master-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate sprint data from multiple project management tools like Linear, Jira, GitHub Projects, and Azure DevOps?

Sprint data consolidation normalizes inputs from multiple tools into a unified analytics model. This Skill ingests data from Linear, Jira, GitHub Projects, and Azure DevOps, applies consistent schema mapping, and produces standardized sprint metrics across all sources so you analyze velocity, burndown, and capacity from one view.

Can I use sprint analytics to forecast velocity and plan capacity across teams?

Velocity forecasting and capacity planning are core sprint analytics functions. This Skill computes historical velocity trends, burndown patterns, and team capacity to generate capacity-aware sprint forecasts and identify planning risks before sprints begin.

What's the best way to prioritize a backlog using multiple factors like dependencies and team capacity?

Multi-factor backlog prioritization combines velocity history, capacity constraints, and dependency analysis to score items. This Skill applies priority scoring during backlog grooming to surface high-impact, achievable work aligned with sprint capacity.

How do I monitor sprint health and generate retrospective reports with actionable insights?

Sprint health monitoring tracks burndown, velocity variance, and risk signals in real time, while retrospective reporting synthesizes sprint outcomes and blockers. This Skill surfaces health alerts and produces retrospective outputs formatted for team review and decision-making.

Does this work with Claude Desktop and CLI, and can it send notifications to Slack or Teams?

Output formatting adapts to Claude Desktop and Claude Code contexts, with optional Slack or Teams notifications for alerts and reports. This Skill delivers context-aware reports and routing so sprint insights reach teams through their existing communication channels.

What input formats does sprint analytics support, and how is data normalized?

Sprint analytics accepts Linear, Jira, GitHub Projects, and Azure DevOps data exports. Normalization maps each tool's schema to a common sprint analytics model, resolving field differences so velocity, capacity, and burndown compute consistently across all sources.