Implement ADO User Story or Task

Fetch Azure DevOps work items and implement them with an approved plan.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/klemensms/mcp-consultant-tools --skill implement-ado-user-story-or-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Implement ADO User Story or Task
Source: https://github.com/klemensms/mcp-consultant-tools/tree/main/.claude/skills/ado-userstory-tasks-implementation
Command: npx skills add https://github.com/klemensms/mcp-consultant-tools --skill implement-ado-user-story-or-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal, end-to-end workflow to implement Azure DevOps user stories or tasks with upfront planning, structured execution, and thorough documentation, ensuring consistent delivery and traceability.

Core Features & Use Cases

  • Structured planning: fetch, analyze, and plan a work item before any changes.
  • End-to-end execution: implement, document progress with HTML-formatted comments, and update release notes.
  • Traceability & governance: generate and maintain plan templates, links, and references for auditing and handoffs.

Quick Start

Present an implementation plan for the given ADO work item and await user approval before starting implementation.

Frequently Asked Questions about Implement ADO User Story or Task

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

FAQPage Schema
How do I implement an Azure DevOps work item with structured planning and release notes?

To implement an Azure DevOps work item, you fetch it by ID via the MCP server to retrieve details and acceptance criteria, then follow a structured workflow of planning, approval, implementation, documentation, and release notes generation.

Can I fetch Azure DevOps parent and child work items for implementation context?

Yes, fetching an Azure DevOps work item by its ID via the MCP server retrieves the description, acceptance criteria, and parent/child context to provide full traceability before implementation begins.

How does the Azure DevOps work item implementation approval process work?

The Azure DevOps implementation workflow presents a structured plan to the user after fetching the work item, and execution only begins after receiving explicit user approval for the proposed implementation strategy.

What is the best way to document progress on Azure DevOps tasks during implementation?

The best way to document Azure DevOps task progress is by posting HTML-formatted progress comments that enforce implementation planning requirements and ensure links and references are formatted for new-tab presentation.

Do I need an MCP server to fetch Azure DevOps work item details for implementation?

Yes, an MCP server connection is required to fetch Azure DevOps work items by their ID, retrieve descriptions and acceptance criteria, and gather the parent/child context needed for structured implementation planning.

What's included in the end-to-end Azure DevOps user story implementation workflow?

The Azure DevOps user story workflow includes structured planning, user approval, code implementation, HTML-formatted progress documentation, release notes updates, and formatted links for auditing and handoffs.