ado-sdlc-discovery

Inventories Azure DevOps projects, repos, pipelines, and boards using read-only Azure CLI queries.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill ado-sdlc-discovery-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-sdlc-discovery
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/azure-devops-cicd/skills/ado-sdlc-discovery
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill ado-sdlc-discovery-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams prescribing CI/CD architecture for Azure DevOps often design from assumptions instead of live evidence. This Skill performs read-only, CLI-first discovery across an Azure DevOps organization so audits and brownfield assessments are grounded in verifiable facts. ## Core Features & Use Cases - CLI-first evidence gathering: Uses Azure CLI with the azure-devops extension first, falling back to Azure DevOps MCP only for gaps and Microsoft Learn MCP for product behavior questions. - Full-SDLC coverage: Inventories projects, teams, repos, branch policies, pipelines, boards, environments, service connections, artifacts, test plans, and wikis. - Structured evidence pack: Produces inventory tables, policy coverage, pipeline shape, access gaps, and not-assessed domains while distinguishing observed facts from permission failures. - Use Case: Before redesigning a client's release process, run discovery to capture branch policy coverage, YAML versus Classic pipeline usage, and service connection configuration without modifying anything. ## Quick Start Use the ado-sdlc-discovery skill to inventory my Azure DevOps organization and project read-only and produce an evidence pack.

Frequently Asked Questions about ado-sdlc-discovery

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

FAQPage Schema
How do I audit an Azure DevOps organization with Azure CLI?

Use the azure-devops CLI extension to list projects, teams, repos, policies, pipelines, and service endpoints with read-only commands like az devops project list and az repos policy list. Verify context first with az account show and az devops configure --list.

How to inventory Azure DevOps pipelines and branch policies?

Run az pipelines list and az pipelines runs list for pipeline shape and run history, and az repos policy list for branch policy coverage such as required reviewers and build validation. Query narrowly first and expand only when evidence requires it.

When should I use Azure DevOps MCP instead of the Azure CLI?

Use Azure DevOps MCP only for gaps or when CLI connectivity or coverage is insufficient, preferably in read-only mode. The CLI with the azure-devops extension remains the primary source of live organization evidence.

Does Azure DevOps discovery require write permissions?

No, discovery is strictly read-only and never queues builds, updates wikis, or modifies resources without explicit approval. Permission failures are reported as access gaps rather than treated as proof a resource does not exist.

Why does discovery show missing data for some Azure DevOps areas?

Missing data usually indicates access gaps from insufficient permissions or areas that were not queried, labeled as not assessed. Apparent absences are confirmed through a second source before driving any high-priority finding.