This was generated by AI during triage.
The triage SKILL documentation lags shipped reality on two points, each pure docs-match-reality (no design decision):
Acceptance: attention-view buckets enumerate every raw marker per the Scope section's dual-axis wording; needs-decision appears in the state machine as a routing outcome; SKILL text is internally consistent.
Sweep-converted from #657.
This was generated by AI during triage.
The triage SKILL documentation lags shipped reality on two points, each pure docs-match-reality (no design decision):
plugins/work-items/skills/triage/SKILL.mddo not list the priority-axis raw marker that PR fix(work-items): re-key triage scope on state, not authorship (#486) #802's merged Scope section already defines (priority:needs-triage), so a repo filing raw intake under that axis is invisible to the no-arg attention view. Add it to the bucket list + filtering instructions, mirroring the Scope section's dual-axis wording.status:needs-decisionas a routing outcome even though the label is live and in active use (e.g. Adopt the documentation-existence admission test as a portable-baseline pre-check in doc-drift and declutter tooling #505). Document it as a recognized routing outcome.Acceptance: attention-view buckets enumerate every raw marker per the Scope section's dual-axis wording;
needs-decisionappears in the state machine as a routing outcome; SKILL text is internally consistent.Sweep-converted from #657.