omc-ado-triage

OMC ADO Triage

Perform a full Azure DevOps triage cycle for the current project. Reads .omg/config.json for connection settings, queries all relevant ADO surfaces (work items, PRs, pipelines, security), and presents a prioritized summary with recommended actions.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Trigger Patterns

• "ado triage"
• "triage work items"
• "check ado board"
• "ado status"
• "work item triage"
• "omc-ado-triage"

---

Step 1: Load Configuration

Read .omg/config.json:

node -e "const f=require('fs');try{process.stdout.write(f.readFileSync('.omg/config.json','utf8'))}catch{console.log('NOT_FOUND')}"

Extract from the ado key:

• org — full org URL (e.g. https://dev.azure.com/contoso)
• project — ADO project name
• repo — repository name
• workItemType — default type filter (e.g. User Story)
• areaPath — area path filter (optional)
• iterationPath — iteration path filter (optional)

If config is NOT_FOUND or missing the ado key: tell the user to run /oh-my-copilot:omc-ado-setup first and stop.

---

Step 2: Gather Triage Data

Run all data-gathering queries in parallel (they are independent). Use MCP tools when available; fall back to az CLI commands.

2a. Untriaged Work Items

Priority 0 — items with no State or still in New with no sprint assignment.

MCP (preferred):

mcp__azure-devops__wit_my_work_items
  → filter: state = "New", no iteration assigned

az CLI fallback:

az boards query \
  --wiql "SELECT [System.Id],[System.Title],[System.WorkItemType],[System.CreatedDate] \
          FROM WorkItems \
          WHERE [System.TeamProject] = '{project}' \
          AND [System.State] = 'New' \
          AND [System.IterationPath] = '{project}' \
          ORDER BY [System.CreatedDate] ASC" \
  --project "{project}" --org "{org}" -o json 2>&1

2b. My Active Work Items