Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Triage Labels

The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo’s GitHub Issues.

Label in mattpocock/skillsLabel in our trackerMeaning
needs-triageneeds-triageMaintainer needs to evaluate this issue
needs-infoneeds-infoWaiting on reporter for more information
ready-for-agentready-for-agentFully specified, ready for an AFK agent
ready-for-humanready-for-humanRequires human implementation
wontfixwontfixWill not be actioned

When a skill mentions a role (e.g. “apply the AFK-ready triage label”), use the corresponding label string from this table.

All five labels exist in the repository. Create none of them; gh label create fails on a label that is already there.

The rest of the taxonomy

Two more label families are in use, and a new issue should carry one from each.

FamilyLabels
priority:priority:high, priority:medium, priority:low, priority:very-low
scope:scope:adr, scope:ci, scope:cli, scope:init, scope:obsidian, scope:performance, scope:policy, scope:source, scope:state, scope:testing, scope:tooling, scope:vscode

Read the live list with gh label list before applying one, because the families grow.

Terminal states are decisions

This repository records decisions as ADRs under docs/adr/, and the two terminal triage outcomes are decisions.

Closing as done. When the work settled a question about how criv behaves — what a command does, what it refuses to do, what a generated artifact looks like — write an ADR before closing. Pure implementation of an already-decided behavior does not need one; changing or establishing a behavior does.

Closing as wontfix. A wontfix is a decision not to do something, and the reasoning is worth more than the label. Write an ADR recording what was proposed and why it was rejected, then close with a link to it.

Both cases follow the normal ADR workflow:

  • criv query next-adr-id for the number; never guess it.
  • Required frontmatter is id, kind: decision, title, status, date.
  • Use governs: for the path globs the decision controls.
  • Accepted ADRs are immutable under ADR-0012. To change a past decision, write a new ADR with supersedes: pointing at the old one — never edit it.
  • Run criv check before finishing.

An issue closed as done or wontfix should link the ADR that settled it, so the reasoning survives the issue being closed.