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.
npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-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.
core_list_projects.core_list_projects to return a list of projects the user can choose from.core_list_project_teams.core_list_project_teams for the selected project so the user can pick a team.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.wit_backlog with action list_work_items for the resolved project and team, using backlog level Microsoft.RequirementCategory (the Requirements / Product Backlog Items level).System.State = ActiveSystem.AssignedTo matches the current userSystem.WorkItemType is one of: Product Backlog Item, Bugwit_work_item with action get_batch for all filtered item IDs with expand=relations and the following fields:System.IdSystem.TitleSystem.StateSystem.AssignedToSystem.WorkItemTypeSystem.ChangedDateSystem.IterationPathMicrosoft.VSTS.Common.PrioritySystem.Parentrelations of each item, collect all parent IDs (System.LinkTypes.Hierarchy-Reverse) and child IDs (System.LinkTypes.Hierarchy-Forward). Call wit_work_item with action get_batch once with the combined set of those IDs (excluding any IDs already fetched) to get their System.Id, System.Title, and System.State.Sort all items by Microsoft.VSTS.Common.Priority ascending (Priority 1 first). For each item, display:
| 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:
{ParentID} {Parent Title}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}.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take microsoft/boards-backlog-summary from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.