---
type: reference
title: Triage label vocabulary
description: The five canonical triage roles and the exact Gitea label strings applied to dank/command-center issues.
tags:
  - skills
  - gitea
  - triage
  - agents
timestamp: 2026-10-20
verified: 2026-10-20
---

# Triage labels

Canonical vocabulary, unchanged: the label string equals the role name. Created
on `dank/command-center` on 2026-10-20 — the repo carried zero labels before that,
so nothing collides and nothing needs renaming.

| Label | Means |
|---|---|
| `needs-triage` | filed, not yet read by a human or agent |
| `needs-info` | blocked on a question back to the reporter |
| `ready-for-agent` | specified enough to implement without further decisions |
| `ready-for-human` | needs a human decision, credential, or judgement first |
| `wontfix` | decided against; keep the record, close it |

The `triage` skill applies and removes these strings directly, so a label must
exist on the tracker before it can be applied:

```bash
curl -sS -K "$cfg" -X POST -H 'content-type: application/json' \
  -d '{"name":"ready-for-agent","color":"0e8a16"}' \
  http://192.168.0.143:3000/api/v1/repos/dank/command-center/labels
```

Renaming is a two-sided edit — change the strings here *and* on the tracker, or
`triage` starts failing to apply them. Adding near-duplicates (`needs-reinfo`,
`ready-for-ai`) is worse than either option: two labels for one role means no
issue reliably carries either.