alex
864447de71
CI / check (push) Has been cancelled
The engineering skills (to-tickets, triage, spec, wayfinder) need to know where issues live for this repo. It is not the Gitea forge remote; it is bd/beads, which AGENTS.md already mandates for all task tracking. Adds docs/agents/issue-tracker.md (bd commands and wayfinding mapping), docs/agents/triage-labels.md (five canonical roles kept as-is, applied with bd tag / bd label add), docs/agents/domain.md (single-context layout: CONTEXT.md plus docs/adr/ at the root), and an 'Agent skills' index block in AGENTS.md. The pre-existing staged deletion of CLAUDE.md is left out of this commit and stays in the index.
1.5 KiB
1.5 KiB
Triage Labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
| Label in mattpocock/skills | Label in our tracker | Meaning |
|---|---|---|
needs-triage |
needs-triage |
Maintainer needs to evaluate this issue |
needs-info |
needs-info |
Waiting on reporter for more information |
ready-for-agent |
ready-for-agent |
Fully specified, ready for an AFK agent |
ready-for-human |
ready-for-human |
Requires human implementation |
wontfix |
wontfix |
Will not be actioned |
When a skill mentions a role (for example "apply the AFK-ready triage label"), use the corresponding label string from this table.
Edit the right-hand column to match whatever vocabulary you actually use.
Applying labels with bd
Labels are bd labels, not forge labels:
bd tag <issue-id> ready-for-agent
bd label add <issue-id> needs-triage
bd label remove <issue-id> needs-triage
bd label list <issue-id>
On creation: bd create "title" -l ready-for-agent.
A ticket has at most one triage role label. When a ticket moves to a new role, remove the old label and add the new one in the same step rather than stacking role labels.