triagelisted

# Triage Analyze requirements for completeness. Explore code + docs, surface gaps, ask clarifying questions, save report. ## Input Detection Argument is `$ARGUMENTS`. | Form | Source | | ------------------------------------- | ------------------------------- | | empty | prompt user to paste / describe | | numeric (`12345`) | Azure DevOps work item id | | URL containing `_workitems/edit/<id>` | Azure DevOps URL → extract id | | path ending `.md` | local markdown spec file | | anything else | treat as pasted text | Ambiguous → ask. Do NOT guess. ## Workflow ### 1. Resolve input #### empty Prompt: "Paste requirements / spec text, or give a ticket id, URL, or .md path." #### Azure DevOps id / URL Invoke `az-cli` skill for reference, then: ```bash az boards work-item show --id <id> --expand all -o json ``` Extract title, description, acceptance criteria, state, type, assignedTo, areaPath, iterationPath, relations. HTML descriptions → readable text. **Always search Confluence** (Atlassian MCP tools) for related docs: - by ticket title keywords - by area path / feature name - by domain terms from description - additional terms from `$ARGUMENTS` if provided Look for: technical specs, ADRs, related-feature docs, business rules, prior decisions. #### `.md` path Read file. Use file content as