
Boards My Work
Pull Azure DevOps work items assigned to you into a sorted, linked table after resolving the correct project via MCP.
Install
npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-my-workWhat is this skill?
- Uses Azure DevOps MCP tools: core_list_projects, wit_my_work_items, wit_get_work_items_batch_by_ids
- Accepts user-supplied project name and skips project listing when the name is explicit
- Prompts for project when missing; blocks until a project is chosen or listed
- Fetches batch field details and renders a formatted table with clickable work item links
- Organizes items by type and sorts by recently changed
Adoption & trust: 35 installs on skills.sh; 23 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
My Work is a Build PM affordance—developers triage assigned backlog items while implementing—not a launch or growth marketing task. PM subphase covers day-to-day sprint visibility: what is on your plate in Azure Boards before you code or review.
Common Questions / FAQ
Is Boards My Work safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Boards My Work
# Get my work items Before getting work items, you need to know which project to use. - If the user **provides a project name** in their request (for example, "for Contoso"), **use that project directly and do not call** the `core_list_projects` tool. - If a project name is **not** provided, first return a prompt asking the user for the project name. - If the project name is still not provided after prompting the user, then call the MCP Server tool `core_list_projects` to get the list of projects the user can choose from. - Do not continue if the user has not provided a project name or selected one from the list. # 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. - `wit_my_work_items`: Get work items from Azure DevOps that are assigned to the user - `wit_get_work_items_batch_by_ids`: Get work item details in batch by their IDs. Use this tool to get detailed information about the work items retrieved by `wit_my_work_items`. # Fields When using the tool `wit_get_work_items_batch_by_ids`, if the user does not provide a list of fields to retrieve, use the following default fields: - System.Id - System.Title - System.State - System.AssignedTo - System.WorkItemType - System.CreatedDate - System.ChangedDate - System.Tags - Microsoft.VSTS.Common.Priority # Display results When displaying the results... - show the work item ID (make this clickable hyperlink to open the work item in a web browser. Format should be like this: [{ID}](https://dev.azure.com/{organization}/{project}/_workitems/edit/{ID})), - title - state, - priority in a table format. Show the most recently changed work items first and group the work items by thier work item type (System.WorkItemType). For example, group the work items into the following categories based on their work item type: Epics Features Stories Bugs Tasks Test Cases other work item types # Steps 1. Check if the user has provided a project name in their request. If not, prompt the user to provide a project name. 2. If the user still does not provide a project name, call the `core_list_projects` tool to get the list of projects and prompt the user to select one. 3. Once a project name is obtained, call the `wit_my_work_items` tool to retrieve the work items assigned to the user for that project. Use `assigned to me` as the filter criteria to get the relevant work items. 4. Extract the IDs of the retrieved work items and call the `wit_get_work_items_batch_by_ids` tool to get detailed information about those work items, including the default fields if the user did not specify any. 5. Organize the retrieved work items by their work item type (System.WorkItemType) and sort them by the most recently changed date (System.ChangedDate). 6. Display the work items in a table format, showing the ID (as a clickable hyperlink), title, state, and priority for each work item, grouped by their work item type.