Skip to content

spec: triage owns backfilling a missing scope label #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mkovero merged 1 commit into from
Aug 30, 2026
Merged

spec: triage owns backfilling a missing scope label #402

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Agent specs for `ac` repo. Each file define role, inputs, outputs, hard constrai

| file | role | trigger |
|---|---|---|
| `.agents/triage.md` | PM — writes specs, routes issues | new issue opened |
| `.agents/triage.md` | PM — writes specs, routes issues, owns the scope label | new issue opened; any issue it touches that has no scope label |
| `.agents/architect.md` | design review — resolves module/interface questions | issue labeled `needs-design` |
| `.agents/ux.md` | output-surface design — what the operator sees, and in what units | issue labeled `needs-ux` |
| `.agents/developer.md` | implementation — one issue per invocation | issue labeled `ready-to-implement` |
Expand Down
10 changes: 10 additions & 0 deletions .agents/triage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,16 @@ all of them, and QA's standards check keys off this:
governs). Unsure between `tier-1` and anything else → `tier-1`; the cost is a
standards check nobody needed, not a missed one.

**An issue with no scope label is yours to fix, whatever else you were doing.**
The label was introduced after these issues were filed, so most of the backlog
predates it; an issue can also lose one when a human edits labels by hand. So
this is not a one-off migration with an end date — treat a missing scope label
the same whether the issue was opened a minute ago or a month ago. Set it and
say so in a one-line comment. QA reads a missing label as `tier-1` and checks
anyway, so this never blocks: you are converting a correct-but-expensive
default into a cheap one, and that is worth exactly one line of comment, not a
re-triage of the issue's spec.

Then, additively — issue change what a user see (stdout format, new display
field, `ac-scene` readout, axis label, banner or fault text) → also apply
`needs-ux`. This is the same condition as category `output-format`, but not
Expand Down