skills.rest
andres-vv
andres-vvCOMMUNITY
Explore all skills by this author →
GitHub

ado-project-scope

Enforce Azure DevOps project and team scope for tool interactions.

3|1|Updated Jan 31, 2026
Search Tags:#configuration#azure devops#work items#ado#sprint#project scope
One-click install
npx skills add https://github.com/andres-vv/Flowkify-mission-10x --skill ado-project-scope
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ado-project-scope
Source: https://github.com/andres-vv/Flowkify-mission-10x/tree/main/skills/ado-project-scope
Command: npx skills add https://github.com/andres-vv/Flowkify-mission-10x --skill ado-project-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all interactions with Azure DevOps tools consistently use the predefined project and team, preventing errors and maintaining focus on the correct work items and resources.

Core Features & Use Cases

  • Enforces Project Scope: Automatically applies the correct ADO_PROJECT and ADO_TEAM to Azure DevOps tool calls.
  • Standardizes Work Item Referencing: Ensures user stories are referenced using the AB#[ticket_number] format.
  • Streamlines Work Item Creation: Defaults new work items to 'User Story' type and assigns them to the current sprint.
  • Use Case: When asking the AI to "List all open bugs," this Skill ensures the query is run against the configured Azure DevOps project, not a default or previously used one.

Quick Start

Use the ado-project-scope skill to ensure all subsequent Azure DevOps commands target the correct project and team.

Frequently Asked Questions about ado-project-scope

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure Azure DevOps queries run against a specific project?▼

To ensure Azure DevOps queries target a specific project, you need a configuration that enforces ADO_PROJECT and ADO_TEAM parameters for all tool interactions. This prevents queries from running against default or previously used projects.

What is the correct syntax for referencing Azure DevOps user stories?▼

The correct syntax for referencing Azure DevOps user stories is the AB#[ticket_number] format. Standardizing work item references ensures that automated ticket tracking and tool calls accurately map to the intended user stories.

How do I automate sprint assignment for new Azure DevOps work items?▼

You can automate sprint assignment by applying a configuration that defaults new work items to the User Story type and assigns them directly to the current sprint during creation.

Can I enforce a default work item type when creating Azure DevOps tickets?▼

Yes, you can enforce a default work item type by applying a project scope configuration. This setup defaults all newly created work items to the User Story type within the defined Azure DevOps project context.

Why do my Azure DevOps work item queries return results from the wrong project?▼

Azure DevOps work item queries return wrong project results when tool calls lack an enforced project context. Applying a predefined ADO_PROJECT and ADO_TEAM scope ensures all queries target the correct project resources.

Related Skills

Explore More Product & Management Skills→
marcussheppmarcusshepp
3

initialize-azure-devops

Configures Azure DevOps organization and project context with a PAT.

Community
Intermediate
thomasholknielsenthomasholknielsen
6

azure-devops

Configure Azure DevOps work items, pipelines, and branch policies.

Community
Advanced
shellicarshellicar

backlog-management

Query and prioritize Azure DevOps backlog items using Azure CLI.

Community
Intermediate
VvanlaarVvanlaar

ado

Automate Azure DevOps work item edits, comments, links, and WIQL queries.

Community
Intermediate