azure-devops-workflow

Manage Azure DevOps work item states, transitions, and branch naming conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jamesbondev/ai-dotfiles --skill azure-devops-workflow-jamesbondev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-devops-workflow
Source: https://github.com/jamesbondev/ai-dotfiles/tree/main/.github/skills/azure-devops-workflow
Command: npx skills add https://github.com/jamesbondev/ai-dotfiles --skill azure-devops-workflow-jamesbondev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidelines and conventions for managing Azure DevOps work items, transitions, and branch naming, ensuring consistency and efficiency in development workflows.

Core Features & Use Cases

  • Work Item Management: Defines work item types (PBI, Spike) and their states (New, Ready, In Progress, etc.).
  • Branching Strategy: Specifies naming conventions for both regular and hotfix branches.
  • Workflow Enforcement: Outlines valid transitions between work item states and predecessor validation.
  • Use Case: When starting a new task, you can use this Skill to ensure your branch name follows the backlog/{workitem_id}-{short-description} format and that you correctly transition the work item from 'Ready' to 'In Progress'.

Quick Start

Use the azure-devops-workflow skill to create a new branch for work item 12345 with the description 'implement user authentication'.

Frequently Asked Questions about azure-devops-workflow

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

FAQPage Schema
How do I create a branch in Azure DevOps linked to a work item?

You transition Azure DevOps work items by following predefined valid state paths, such as moving a PBI or Spike from Ready to In Progress, and linking the associated pull request to maintain workflow consistency.

What is the correct naming convention for Azure DevOps hotfix branches?

This skill manages Azure DevOps work item states, transitions, and branch naming conventions for efficient software development. It enforces predefined workflow states and branch naming formats to ensure consistency across tasks like picking up work items and linking pull requests.

How do I transition Azure DevOps work item states correctly?

To create a branch in Azure DevOps linked to a work item, use the predefined naming convention format such as backlog/{workitem_id}-{short-description} to ensure consistency and traceability across your development workflow.

What is the standard workflow for picking up Azure DevOps work items?

The correct naming convention for Azure DevOps hotfix branches follows a specified format that distinguishes them from regular branches, ensuring clear identification and consistent branch management across the repository.