ado

Automate Azure DevOps work item management via MCP tool calls.

Updated Aug 27, 2026

Search Tags:#automation #devops #mcp #quality-assurance #ado #work-item #dreamland

Ready to run

npx skills add https://github.com/aiguy611/cc-tools --skill ado-aiguy611

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ado
Source: https://github.com/aiguy611/cc-tools/tree/main/.github/skills/ado
Command: npx skills add https://github.com/aiguy611/cc-tools --skill ado-aiguy611

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines manual ADO work item operations by converting natural language requests into MCP tool calls, applying Dreamland defaults to reduce setup time and errors.

Core Features & Use Cases

Create, update, query, and link work items across Feature, User Story, Bug, Task, Epic, and more; batch-create child items; validate area/iteration paths; detect duplicates; verify results; and persist logs for audit.

Quick Start

Describe the ADO task you want to perform in a natural language sentence and let the skill translate it into MCP calls.

Frequently Asked Questions about ado

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

FAQPage Schema

How do I automate Azure DevOps work item creation from natural language requests?▼

Azure DevOps work item automation converts natural language requests into MCP tool calls to create, update, query, and link Features, User Stories, Bugs, Tasks, and Epics with Dreamland defaults and pre-flight validations.

What's the best way to manage ADO work items without manual portal navigation?▼

ADO work item management is handled by translating natural language sentences into MCP tool calls, applying Dreamland defaults to reduce manual setup time and enforce area/iteration validation, duplicate checks, and post-creation verification.

Can I batch-create child work items under a Feature or Epic using MCP?▼

Batch-creating child work items under parent Features or Epics is supported through natural language requests translated into MCP tool calls, with duplicate detection and persistence to qmd logs for audit purposes.

Does the ADO automation skill validate area and iteration paths before creating work items?▼

Area and iteration path validation is enforced as a pre-flight check before any work item write operation, ensuring that created or updated Features, User Stories, Bugs, and Tasks conform to Dreamland defaults and project structure.

Why does the MCP work item automation require explicit confirmation before writing to Azure DevOps?▼

Explicit user confirmation before writes prevents unintended modifications to Azure DevOps work items, ensuring that all create, update, and link operations generated from natural language are reviewed and verified before execution.

What work item types are supported by natural language ADO automation with Dreamland defaults?▼

Supported work item types include Feature, User Story, Bug, Task, and Epic, all manageable through natural language requests that enforce Dreamland defaults, duplicate checks, and post-creation verification with qmd persistence.