Start with the outcome your team needs. Each workflow defines its trigger, Azure DevOps context, execution method, actions, approval boundary, verification, and run record.
Each family groups representative outcomes and names the Azure DevOps services it works across. Workflows run under the Boards tab; every run creates a Job with logs.
Backlog readiness, acceptance criteria, epic decomposition, duplicate detection, requirements quality, dependencies, and change impact.
PR review, work-item linkage, code-owner routing, defect investigation, code change impact, security findings, and follow-up work.
Pipeline diagnosis, run comparison, build configuration audit, remediation, deployment readiness, release planning, notes, rollback, and approval verification.
Test generation, coverage gaps, test-run execution, failed-test triage, flaky-test diagnosis, defect creation, regression analysis, and sign-off reports.
Incident investigation, change correlation, runbook maintenance, status updates, approved remediation, and recurring operational checks.
Traceability audits, baseline checks, branch and approval controls, standards mapping, validation readiness, and evidence-package assembly.
Every workflow is described by the same catalog-card fields, so you compare by outcome and control — not by agent count. Here is one card for a pipeline-failure recovery workflow.
| Field | Pipeline-failure recovery |
|---|---|
| Outcome | Diagnose and remediate common Azure Pipeline failures. |
| Trigger | Pipeline failed; manual run; scheduled health review. |
| Reads | Failed run, task logs, previous successful run, commit, PR, linked work items. |
| Actions | Post diagnosis, create task, prepare branch/PR, rerun after approval. |
| Execution model | Planner agent with deterministic verification. |
| Approval | Required before code/configuration change or rerun in protected scope. |
| Azure DevOps services | Pipelines, Repos, Boards. |
Filter workflows by Azure DevOps service, trigger, execution model, action level, role, industry, standard, approval requirement, and output type — never by agent count.
Triggers are manual, an Azure DevOps event, or scheduled. Every run creates a Job with logs, whichever execution model the workflow uses.
A useful demo shows the current manual process, the configured agent run, the approval boundary, and the verification result.