/ado-resource-validator

description: Validates Azure DevOps projects, area paths, and teams exist with auto-creation of missing resources. Use when setting up ADO integration, configuring .env variables, or troubleshooting missing project errors. Supports project-per-team, area-path-based, and team-based strategies.
version: 1.0.0
user-invokable: false
allowed-tools: Read, Bash, Write, Edit

Azure DevOps Resource Validator Skill

**Purpose**: Validate and auto-create Azure DevOps projects and resources, ensuring .env configuration is correct.

**Auto-Activation**: Triggers when Azure DevOps setup or validation is needed.

What This Skill Does

This skill ensures your Azure DevOps configuration in `.env` is valid and all resources exist. It's **smart enough** to:

1. **Validate Azure DevOps projects** - Check if projects exist (multiple for project-per-team) 2. **Prompt for action** - Select existing project or create new one 3. **Validate area paths** - Check if area paths exist (for area-path-based strategy) 4. **Create missing area paths** - Auto-create area paths if missing 5. **Validate teams** - Check if teams exist (for team-based strategy) 6. **Update .env with correct values** - Ensure configuration is valid

When This Skill Activates

✅ **Automatically activates when**:

• You set up Azure DevOps integration for the first time
• You run `sw-ado:sync` and resources are missing
• Your `.env` has invalid Azure DevOps configuration
• You mention "ado setup" or "azure devops validation"

Azure DevOps Configuration Structure

Required .env Variables

AZURE_DEVOPS_PAT=your_token_here
AZURE_DEVOPS_ORG=yourorganization
AZURE_DEVOPS_STRATEGY=project-per-team  # or area-path-based, team-based

Strategy-Specific Variables

**Strategy 1: Project-per-team** (Multiple Projects)

AZURE_DEVOPS_STRATEGY=project-per-team
AZURE_DEVOPS_PROJECTS=WebApp,MobileApp,Platform

→ Validates that WebApp, MobileApp, and Platform projects exist

**Strategy 2: Area-path-based** (One Project, Multiple Area Paths)

AZURE_DEVOPS_STRATEGY=area-path-based
AZURE_DEVOPS_PROJECT=MainProduct
AZURE_DEVOPS_AREA_PATHS=Frontend,Backend,Mobile

→ Validates MainProduct project exists → Creates area paths if missing: MainProduct\Frontend, MainProduct\Backend, MainProduct\Mobile

**Strategy 3: Team-based** (One Project, Multiple Teams)

AZURE_DEVOPS_STRATEGY=team-based
AZURE_DEVOPS_PROJECT=MainProduct
AZURE_DEVOPS_TEAMS=Alpha Team,Beta Team,Gamma Team

→ Validates MainProduct project exists → Creates teams if missing: Alpha Team, Beta Team, Gamma Team

**NEW: Per-Project Configuration** (Advanced - Multiple Projects × Resources)

# Multiple projects with their own area paths and teams
AZURE_DEVOPS_STRATEGY=project-per-team
AZURE_DEVOPS_PROJECTS=Backend,Frontend,Mobile

# Per-project area paths (hierarchical naming)
AZURE_DEVOPS_AREA_PATHS_Backend=API,Database,Cache
AZURE_DEVOPS_AREA_PATHS_Frontend=Web,Admin,Public
AZURE_DEVOPS_AREA_PATHS_Mobile=iOS,Android,Shared

# Per-project teams (optional)
AZURE_DEVOPS_TEAMS_Backend=Alpha,Beta
AZURE_DEVOPS_TEAMS_Frontend=Gamma

→ Validates 3 projects exist: Backend, Frontend, Mobile → Creates area paths per project:

• Backend\API, Backend\Database, Backend\Cache
• Frontend\Web, Frontend\Admin, Frontend\Public
• Mobile\iOS, Mobile\Android, Mobile\Shared

→ Creates teams per project:

• Backend: Alpha, Beta
• Frontend: Gamma

**Naming Convention**: `{PROVIDER}_{RESOURCE_TYPE}_{PROJECT_NAME}`

Validation Flow

Step 1: Strategy Detection

**Read .env and detect strategy**:

AZURE_DEVOPS_STRATEGY=project-per-team

**Result**:

🔍 Detected strategy: Project-per-team
   Projects to validate: WebApp, MobileApp, Platform

Step 2: Project Validation (Project-per-team)

**Check if projects exist**:

# API calls to Azure DevOps
GET https://dev.azure.com/{org}/_apis/projects/WebApp
GET https://dev.azure.com/{org}/_apis/projects/MobileApp
GET https://dev.azure.com/{org}/_apis/projects/Platform

**If all projects exist**:

✅ All projects validated:
   • WebApp (ID: abcd1234)
   • MobileApp (ID: efgh5678)
   • Platform (ID: ijkl9012)

**If some projects don't exist**:

⚠️ Projects not found:
   ✅ WebApp (exists)
   ❌ MobileApp (not found)
   ❌ Platform (not found)

What would you like to do?
1. Create missing projects
2. Select existing projects
3. Fix project names manually
4. Cancel

Your choice [1]:

**Option 1: Create Missing Projects**:

📦 Creating Azure DevOps projects...

Creating project: MobileApp...
✅ Project created: MobileApp (ID: mnop3456)

Creating project: Platform...
✅ Project created: Platform (ID: qrst7890)

✅ All projects now exist!

**Option 2: Select Existing Projects**:

Available projects in organization:
1. WebApp
2. ApiGateway
3. AuthService
4. NotificationService
5. DataPipeline

Select projects (comma-separated numbers) [2,3]:

✅ Updated .env: AZURE_DEVOPS_PROJECTS=WebApp,ApiGateway,AuthService

Step 3: Area Path Validation (Area-path-based)

**Scenario**: One project with area paths

AZURE_DEVOPS_STRATEGY=area-path-based
AZURE_DEVOPS_PROJECT=MainProduct
AZURE_DEVOPS_AREA_PATHS=Frontend,Backend,Mobile,QA

**Validation**:

Checking project: MainProduct...
✅ Project "MainProduct" exists

Checking area paths...
  ✅ MainProduct\Frontend (exists)
  ✅ MainProduct\Backend (exists)
  ⚠️ MainProduct\Mobile (not found)
  ⚠️ MainProduct\QA (not found)

📦 Creating missing area paths...
✅ Created: MainProduct\Mobile
✅ Created: MainProduct\QA

✅ All area paths validated/created successfully

Step 4: Team Validation (Team-based)

**Scenario**: One project with multiple teams

AZURE_DEVOPS_STRATEGY=team-based
AZURE_DEVOPS_PROJECT=MainProduct
AZURE_DEVOPS_TEAMS=Alpha Team,Beta Team,Gamma Team

**Validation**:

Checking project: MainProduct...
✅ Project "MainProduct" exists

Checking teams...
  ✅ Alpha Team (exists)
  ⚠️ Beta T