name: ado-project-scope
description: When using Azure DevOps MCP (user-ado) tools, always use project XXX and team XXX Team unless the user explicitly asks for another project. Use when calling ADO tools, work items, repos, backlogs, queries, or when the user mentions Azure DevOps, XXX, or ADO in this project.

Azure DevOps MCP — XXX project scope

Scope

When using the user-ado (Azure DevOps) MCP server in this project, always restrict operations to the XXX project.

Default values

Instructions

1. Every ADO tool call: Pass project: "XXX" when the tool accepts a project parameter.
2. Tools that need a team (e.g. wit_list_backlog_work_items, wit_list_backlogs, wit_get_work_items_for_iteration, core_list_project_teams): Also pass team: "XXX Team" when the tool accepts a team parameter.
3. Search/filter tools (e.g. search_workitem): Use project: ["XXX"] in the project filter.
4. Override: Use a different project or team only when the user explicitly asks (e.g. "list issues in project X" or "show me the OtherProject board").
5. Creating work items: When creating a new ticket/work item:
6. Always create a User Story unless the user explicitly specifies a different work item type (e.g. Bug, Task, Epic).
7. Assign it to the current sprint based on today's date. Use wit_list_team_iterations to find the active iteration whose date range includes the current date, then set the System.IterationPath field accordingly.

Examples

• "List work items" → call with project: "XXX".
• "List repos" → use project XXX.
• "Run query X" → pass project: "XXX".
• "List issues in Contoso" → use project "Contoso" (user override).