aurelienclere-365/ado-cowork-plugin/ado-project-discovery

ADO Project Discovery

List and explore Azure DevOps projects and team structure across an organisation.

When to use

• User wants to know which projects exist in their ADO organisation
• User needs to find the right project before creating work items or browsing repos
• User wants to see the teams inside a project
• User is onboarding and needs an overview of the organisation structure

MCP tools used

Workflow

1. List projects. Call core_list_projects to get the full project list with IDs, names,

state (active/deleted), and visibility.

1. Filter if needed. If the user named a specific project, match by name (case-insensitive).

If ambiguous, present the full list and ask the user to confirm.

1. List teams (if asked). Call core_list_project_teams(projectId) to get team names,

team IDs, and descriptions. Present as a flat table.

1. Surface next steps. After listing, suggest follow-up actions the user can take:

browse repos, create work items, check pipelines in the project.

Output Format

Projects

Teams in a project

Notes

• Use the project name and ID returned here as inputs to other skills

(ado-work-items, ado-pipelines, ado-repositories, etc.).

• If the organisation has a large number of projects (>20), ask the user for a keyword

to filter before presenting results.

• core_list_projects returns projects across all process templates (Agile, Scrum, CMMI).

Active context

This skill also powers the implicit context resolution used by all other skills.

• After listing and selecting a project here, the result can be passed to ado-context

to store it as the session-wide active project.

• Suggest: "To avoid specifying the project every time, say: 'set active project Platform'."