Azure DevOps Work Items

Create Azure DevOps work items with HTML-formatted fields and parent-child hierarchy.

34|3|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/charlesjones-dev/claude-code-plugins-dev --skill azure-devops-work-items
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Azure DevOps Work Items
Source: https://github.com/charlesjones-dev/claude-code-plugins-dev/tree/main/plugins/ai-ado/skills/ado-work-items
Command: npx skills add https://github.com/charlesjones-dev/claude-code-plugins-dev --skill azure-devops-work-items

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @azure-devops/mcp.

What problem does it solve?

This Skill automates the creation and management of Azure DevOps work items (Features, User Stories, Tasks), ensuring consistent hierarchy, formatting, and naming conventions. This saves significant manual effort, reduces errors, and keeps your backlog organized.

Core Features & Use Cases

  • Structured Work Item Creation: Creates Features, User Stories, and Tasks with proper parent-child relationships, enforcing a logical project hierarchy.
  • HTML Formatting Enforcement: Ensures all text fields (Description, Acceptance Criteria) use correct HTML for optimal rendering and readability in Azure DevOps.
  • Naming Convention Adherence: Applies project-specific naming standards (e.g., decimal notation) for clear backlog organization and easy identification.
  • Use Case: Automatically create a new Feature in Azure DevOps, then break it down into User Stories with acceptance criteria and Tasks with hour estimates, all correctly formatted and linked, saving hours of manual data entry.

Quick Start

Use the Azure DevOps Work Items skill to create a new Feature titled "User Profile Management" with a description explaining its business value.

Frequently Asked Questions about Azure DevOps Work Items

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

FAQPage Schema
How do I create work items with proper hierarchy in Azure DevOps?

Create work items with proper hierarchy by establishing parent-child relationships: Features at the top level, User Stories nested beneath Features, and Tasks nested beneath User Stories. This Skill automates the hierarchy enforcement, ensuring each item links correctly to its parent and maintains logical backlog organization.

What HTML formatting is required for Azure DevOps Description and Acceptance Criteria fields?

Azure DevOps Description and Acceptance Criteria fields require HTML formatting for optimal rendering and readability. This Skill automatically applies correct HTML to these text fields, ensuring consistent formatting across all work items without manual markup entry.

Can I automate the creation of Features, User Stories, and Tasks in Azure DevOps?

Yes. This Skill automates creation of Features, User Stories, and Tasks with consistent naming conventions, HTML-formatted descriptions, parent-child linking, and effort estimation. A single request generates an entire hierarchical work item structure, eliminating hours of manual data entry.

How do I apply naming conventions across my Azure DevOps backlog?

Apply project-specific naming standards such as decimal notation to all work items automatically. This Skill enforces naming conventions during creation, ensuring clear identification and easy backlog organization without requiring manual standardization of each item.

What happens if I don't use HTML formatting in Azure DevOps work items?

Without HTML formatting, Description and Acceptance Criteria fields render poorly in Azure DevOps, reducing readability and professional presentation. This Skill enforces HTML formatting by default, preventing rendering issues and maintaining consistent visual formatting across your backlog.

Can I estimate effort in hours and story points for work items automatically?

Yes. This Skill includes effort estimation fields for work items, supporting both hour estimates for Tasks and story point estimation for User Stories. Estimates are applied during creation, ensuring consistent effort tracking throughout your project hierarchy.