ado-work-items

This skill provides structured guidance for developers and project managers using the Azure DevOps MCP server to maintain high-quality work item tracking. It focuses on enforcing organizational best practices for Agile projects, ensuring that Features, User Stories, and Tasks are linked correctly within a parent-child hierarchy to facilitate clear project visibility and progress reporting.

The tool is designed for teams aiming to maintain consistent documentation and estimation standards across their Azure DevOps boards. By providing templates for description fields and acceptance criteria, it helps teams move away from unstructured plain text toward clean, renderable HTML content that integrates seamlessly with Azure DevOps work item interfaces.

• Standardized hierarchy management for Features, User Stories, and Tasks, ensuring every item has a proper parent relationship.
• Mandatory HTML formatting guidance for work item descriptions and acceptance criteria, utilizing semantic tags like p, ul, li, strong, and em for better readability.
• Best practices for writing acceptance criteria using the Given, When, Then (GWT) format to improve testability and QA collaboration.
• Fibonacci-based story point estimation guidelines (1, 2, 3, 5, 8, 13) to encourage relative sizing and complexity awareness.
• Field setting recommendations for Area Path, Iteration Path, and State management to ensure consistent tracking during sprint planning.
• Integration support for the @azure-devops/mcp server tools, streamlining the creation of items via command-line workflows.

Users should employ this skill during sprint planning, backlog grooming, or when initializing new development efforts. The skill acts as an operational blueprint to prevent common pitfalls such as orphaned tasks, missing context in story descriptions, or inconsistent formatting that hinders reporting. It is particularly useful for developers who need to quickly generate technical tasks while maintaining compliance with team-wide Agile definitions. Always verify that your work items are assigned to the correct iteration and that the hierarchy matches your team's current project structure to ensure accurate roll-up reporting in your dashboard.