azure-devops-org

Discover and configure Azure DevOps project structures, teams, and backlog settings.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/shellicar/claude-config --skill azure-devops-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-devops-org
Source: https://github.com/shellicar/claude-config/tree/main/skills/azure-devops-org
Command: npx skills add https://github.com/shellicar/claude-config --skill azure-devops-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams quickly discover and align Azure DevOps project structures, including organizations, projects, and team layouts, to accelerate setup and governance.

Core Features & Use Cases

  • Discover project structure: teams, area paths, and iteration paths to understand how work will be organized.
  • Configure team settings: enforce backlog visibility, area/iteration mappings, and standard backlog column options for consistency.
  • Audits and patterns: detect orphaned work items and apply hierarchical team patterns (portfolio vs feature teams) to streamline governance.

Quick Start

Run an audit to enumerate current teams and areas, then apply a standard backlog configuration across the project.

Frequently Asked Questions about azure-devops-org

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

FAQPage Schema
How do I organize Azure DevOps projects into scalable teams and structures?

Configuring backlog visibility in Azure DevOps involves enforcing standard area and iteration path mappings across teams to control which work items appear, streamlining project governance and portfolio management.

Can I audit orphaned work items and team structures in Azure DevOps?

Auditing orphaned work items in Azure DevOps is possible by running a project audit to enumerate current teams, area paths, and iteration paths, detecting structural gaps to apply hierarchical portfolio or feature team patterns.

What is the best way to apply standard backlog column configurations across a project?

Applying standard backlog column configurations across a project requires enforcing consistent team settings, including backlog visibility and area/iteration mappings, to align the portfolio and feature team structures end-to-end.

Does this approach support discovering existing area paths and iteration paths for governance?

Discovering existing area paths and iteration paths is fully supported to understand how work is currently organized, enabling the application of hierarchical team patterns and standard backlog settings for streamlined project governance.

Why does my Azure DevOps backlog visibility show inconsistent work items across teams?

Inconsistent backlog visibility across Azure DevOps teams typically occurs when standard area and iteration path mappings are not enforced, requiring a project audit to realign team settings and apply hierarchical portfolio structures.