
boards-backlog-summary
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.
- Installs
- 55
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-backlog-summary- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads boards-backlog-summary automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Get team backlog summary
This skill retrieves the team's Requirements-level backlog, filters to Active items assigned to the current user, enriches them with parent and child work item details, and displays them sorted by priority.
Project selection
- If the user provides a project name in their request (for example, "for Contoso"), use that project directly and do not call
core_list_projects. - If the project name is not provided, ask the user once to provide it.
- If the project name is still not provided after asking once, call
core_list_projectsto return a list of projects the user can choose from. - Do not continue if no project has been provided or selected.
Team selection
- If the user provides a team name, use it directly and do not call
core_list_project_teams. - If the team name is not provided, ask the user once to provide it.
- If the team name is still not provided after asking once, call
core_list_project_teamsfor the selected project so the user can pick a team. - Do not continue if no team has been provided or selected.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get the list of projects the user can choose from.core_list_project_teams: Get the list of teams for a project.wit_backlog(action:list_work_items): Get the work items on the team's backlog at a specific backlog level.wit_work_item(action:get_batch): Get work item details in batch by their IDs. Use this to fetch fields and relations for backlog items, their parents, and their children in as few calls as possible.
Steps
-
Resolve project and team using the rules above.
-
Call
wit_backlogwith actionlist_work_itemsfor the resolved project and team, using backlog levelMicrosoft.RequirementCategory(the Requirements / Product Backlog Items level). -
From the returned work items, filter to items that meet all of the following criteria:
System.State=ActiveSystem.AssignedTomatches the current userSystem.WorkItemTypeis one of:Product Backlog Item,Bug
-
If no items match the filter, display a message stating there are no active backlog items assigned to the current user for this team and stop.
-
Call
wit_work_itemwith actionget_batchfor all filtered item IDs withexpand=relationsand the following fields:System.IdSystem.TitleSystem.StateSystem.AssignedToSystem.WorkItemTypeSystem.ChangedDateSystem.IterationPathMicrosoft.VSTS.Common.PrioritySystem.Parent
-
From the
relationsof each item, collect all parent IDs (System.LinkTypes.Hierarchy-Reverse) and child IDs (System.LinkTypes.Hierarchy-Forward). Callwit_work_itemwith actionget_batchonce with the combined set of those IDs (excluding any IDs already fetched) to get theirSystem.Id,System.Title, andSystem.State. -
Display the results as described in the Display results section below.
Display results
Sort all items by Microsoft.VSTS.Common.Priority ascending (Priority 1 first). For each item, display:
{ID} — {Title}
| Field | Value |
|---|---|
| State | {System.State} |
| Priority | {Microsoft.VSTS.Common.Priority} |
| Changed Date | {System.ChangedDate formatted as MM/DD/YYYY} |
| Iteration | {last segment of System.IterationPath} |
| Work Item Type | {System.WorkItemType} |
Parent:
- If a parent exists:
{ParentID}{Parent Title} - If no parent exists: (none)
Child Items:
If there are child items, display them in a table:
| ID | Title | State |
|---|---|---|
| {ChildID} | {Child Title} | {Child State} |
If there are no child items, display: (none)
After all items are listed, display a summary line:
Showing {N} active backlog item(s) assigned to you on team {team name} in project {project name}.
FAQ
What does the boards-backlog-summary skill do?
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.
How do I install boards-backlog-summary?
Run npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-backlog-summary in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/boards-backlog-summary/ (personal) or .claude/skills/boards-backlog-summary/ (project).
Which AI agents can use boards-backlog-summary?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is boards-backlog-summary safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains boards-backlog-summary?
It is published by microsoft in microsoft/azure-devops-skills. It has 55 recorded installs.
More from microsoft/azure-devops-skills
pipelines-build-summary
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
boards-work-item-summary
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
boards-my-work
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
work-iterations
microsoft/azure-devops-skills
List, create, and assign iterations for Azure DevOps projects and teams.
security-alert-review
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
skill-name
microsoft/azure-devops-skills
Description of what the skill does and when to use it
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.