ado-work-itemlisted
Install: claude install-skill viettdann/arclight-kit
# ADO work item
Turn one work item into what the user needs before touching code. The fields are not reliable: items are written by people and AI assistants alike, process templates differ across projects (Scrum, Agile), and nobody keeps state, fields or links tidy. Read for meaning, not for field semantics.
## 1. Fetch
```
python3 ${CLAUDE_SKILL_DIR}/scripts/work-item.py --org ORG --id ID_OR_URL [--comments N] [--parent-chars N] [--download DIR]
```
- Org: from the URL, the repo remote (`https://dev.azure.com/{org}/...`), or `ADO_ORG`. IDs are unique per organization, so the project is not needed.
- Credentials as in `ado-pipelines-advisor`: `AZURE_DEVOPS_EXT_PAT`, else `az login`, with the token taken in the organization's tenant. On exit 2 with an authentication message, ask the user to `az login --tenant <tenant in the message>` or export a PAT with Work Items (Read) and Code (Read); never ask for the PAT in chat.
- Screenshots, recordings, junit or report files matter for a bug: rerun with `--download` to a new directory under `/tmp`, then Read the images and text files. Skip videos.
- The output covers fields, rich-text fields (Description, ReproSteps, AcceptanceCriteria, SystemInfo, custom fields), test steps, up to three ancestors with a description excerpt, linked items, the latest 10 pull requests, attachments, and the newest comments.
## 2. Read it
- **Latest wins.** Comments and "scope change" notes later than the description override it. When they conflict,