ops classify
Classify a ticket description as bug, feature, chore, or docs. Uses AI to determine ticket type and suggest routing. Outputs a classification with confidence and a suggested ADO work item type.
Synopsis
Classify a ticket as bug, feature, chore, or docs
Terminal
$ops classify "<TEXT>"
Arguments
| Argument | Description |
|---|---|
TEXT | Ticket text to classify (required) |
Flags
| Flag | Type | Description | Default |
|---|---|---|---|
--json | flag | Output as JSON for scripts and AI agents | — |
Examples
Expected classification: bug → Issue
Terminal
$ops classify "Sling timeout on large tables"
Expected classification: feature → Issue
Terminal
$ops classify "Add Teams notification for failed Prefect flows"
Expected classification: docs → Task (JSON output)
Terminal
$ops classify "Update CLAUDE.md for wdp-import" --json
ADO Work Item Mapping
The Wasteology ADO project uses the Basic process template, so classifications map to a limited set of work item types:
| Classification | ADO Work Item Type |
|---|---|
bug | Issue |
feature | Issue |
chore | Task |
docs | Task |
Pair With
routeops classify answers "what kind of work is this?". Use ops route to then decide who owns it.