Frank
6f1f55345a
The Matt Pocock engineering skills (triage, to-tickets, to-spec, research, implement) assume per-repo config for three things: where work items live, what the triage label vocabulary is, and where domain docs sit. Nothing here declared any of them, so every skill run re-guessed. Frank's decisions, 2026-10-20: Gitea on Dankclaw as the tracker (no gh, no tea on any box, so it is recorded as prose — auth via a 600 curl config, the endpoint table, the 404-on-empty-token / form-encoded-merge / empty-200-on-merge traps, and the AGENTS.md laws a skill must not renegotiate); the canonical triage label vocabulary kept as-is, with the five labels created on the tracker (the repo had zero, so nothing collides); single-context domain docs. The configuration moved out of the skill's default docs/agents/ and into the one knowledge base this repo allows: three pages under omp-docs/skills/, an empty omp-docs/decisions/ carrying the ADR format rule, an "## Agent skills" pointer block in AGENTS.md, index entries, and a log entry. The glossary is deliberately not created — every candidate term already has an owner in system/, core/ or skills/, and a term list that paraphrases them is a second owner of facts already written down. Known cost: re-running setup-matt-pocock-skills will not recognise omp-docs/skills/* and will offer to recreate docs/agents/; the AGENTS.md pointer is what stops that. Also closes a verification gap found on the way: kb-lint.bats only ever points the linter at fixtures, so a page with no frontmatter or an index that stops listing a file passes the suite silently. Two tests now run the linter and the coverage checker against the shipped omp-docs/ tree. Refs #18
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
---
|
|
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.
|