writing-ado-items

Writes and normalizes Wholesale Architecture Azure DevOps work item titles, ownership, and parent routing.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill writing-ado-items-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-ado-items
Source: https://github.com/leonardoacosta/agents/tree/main/skills/writing-ado-items
Command: npx skills add https://github.com/leonardoacosta/agents --skill writing-ado-items-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Azure DevOps boards accumulate inconsistent work item titles, SNOW identifiers, wrong parents, and unclear ownership. This Skill standardizes Wholesale Architecture ADO items by cleaning titles, routing items to durable epics, and enforcing identity and ownership rules before any write. ## Core Features & Use Cases - Title normalization: Removes brackets, RITM/CHG identifiers, redundant project prefixes, and em dashes while preserving technical meaning and routing identifiers. - Parent and type routing: Maps items to durable epics such as WHS-346, DOC, and Submission Engine using explicit ID mappings before keyword rules. - Ownership-safe writes: Uses native az devops and az boards commands, verifies owner and parent before writes, and reads back every changed item. - Use Case: Given a board full of items like "Execute CHG1234 Monthly VM patching", preview and apply renames to "Monthly VM patching" while keeping change references in the body and confirming each result. ## Quick Start Ask the agent to review and clean up the Wholesale ADO work item titles and parents in the current sprint using the az-ado identity rules.

Frequently Asked Questions about writing-ado-items

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

FAQPage Schema
How do I clean up Azure DevOps work item titles in bulk?

Read current items with az boards, define an owned-only scope, apply explicit ID mappings before keyword rules, then preview old and new titles before writing. After each write, read back the item to confirm the result.

How do I remove RITM and CHG identifiers from ADO titles?

Strip SNOW request and change identifiers such as RITM and CHG from the title, but retain their history, links, or references in the item body when relevant. Never invent deployment scope if a title becomes empty.

Can I use az boards work-item show with --fields and --expand together?

No. The installed Azure CLI rejects combining --fields with --expand on az boards work-item show. Use one option at a time and check current CLI help before running mutations.

When should a work item not be renamed or rerouted?

Skip items not assigned to the two approved identities, items whose parent chain leaves the owned project scope, and items owned by someone else. Record unresolved parent ambiguity separately instead of guessing.

What are the limitations of keyword-based parent routing in Azure DevOps?

Keyword guesses are unreliable for epic routing. Explicit ID mappings take precedence, durable epic names like WHS-346 or DOC must match the live board, and ambiguous parents should be recorded rather than guessed.