Filed by the skills seat (session session_012Gg6rMAti8ZaueWb6BRsDn), 2026-08-12, executing a maintainer ruling from the seat 专题 chat.
Provenance (maintainer, verbatim, untranslated)
还有一个问题,每个issue创建时是否都应该标注 bug,项目经理安排任务时是否应该优先bug,还有哪些其他相关的建议
同意
(Approving the seat's recommendation as presented: native types, single producer, tiebreaker not ladder, the three consumer synergies, no mass backfill.)
Fact base: the repo already carries org-level native issue types Bug / Feature / Task (issue_write supports type); no new label axis is created.
Deltas to .claude/skills/pm-dispatch/SKILL.md
1. Triage duty (step-0 section): type every card.
- The triage seat is the single authoritative producer of the
type field (filers may pre-set; triage corrects at classification time — same discipline as domain:*). - Mechanical criterion, citing the existing boundary test (no second copy): wrong behavior against the declared contract ⇒
Bug; grows the accept-set / public surface ⇒ Feature; everything else (docs, tooling, refactor, chores) ⇒ Task. - Bug repro discipline: a
Bug with no named location or repro path does not enter pm:queue — triage flags it for repro instead (premise-first, moved to filing time). - ⛔ No mass backfill of the existing backlog (whole-backlog rescans are the known rot pattern): new cards at filing/triage; existing cards when next touched.
2. Executor selection: Bug-first tiebreaker.
Within ordinary queue items (i.e., below the existing order priority:p0 → unlock fan-out → target:<major> board → named-upstream), Bug outranks Feature/Task. It is a tiebreaker, ⛔ not a priority ladder — fine-grained gradations (P1–P5) were tried and rejected: ungraded-able, they rot.
Named consumers (a classification exists iff something reads it): ① the adjudication lane's routing gate — Feature is mechanically on the human floor, Bug/Task are the auto-adjudicable candidates; ② the release-board producer's defect scan becomes a type:Bug is:open query; ③ the selection tiebreaker above.
Landing notes
Filed by the skills seat (session
session_012Gg6rMAti8ZaueWb6BRsDn), 2026-08-12, executing a maintainer ruling from the seat 专题 chat.Provenance (maintainer, verbatim, untranslated)
(Approving the seat's recommendation as presented: native types, single producer, tiebreaker not ladder, the three consumer synergies, no mass backfill.)
Fact base: the repo already carries org-level native issue types Bug / Feature / Task (
issue_writesupportstype); no new label axis is created.Deltas to
.claude/skills/pm-dispatch/SKILL.md1. Triage duty (step-0 section): type every card.
typefield (filers may pre-set; triage corrects at classification time — same discipline asdomain:*).Bug; grows the accept-set / public surface ⇒Feature; everything else (docs, tooling, refactor, chores) ⇒Task.Bugwith no named location or repro path does not enterpm:queue— triage flags it for repro instead (premise-first, moved to filing time).2. Executor selection: Bug-first tiebreaker.
Within ordinary queue items (i.e., below the existing order
priority:p0→ unlock fan-out →target:<major>board → named-upstream),BugoutranksFeature/Task. It is a tiebreaker, ⛔ not a priority ladder — fine-grained gradations (P1–P5) were tried and rejected: ungraded-able, they rot.Named consumers (a classification exists iff something reads it): ① the adjudication lane's routing gate —
Featureis mechanically on the human floor,Bug/Taskare the auto-adjudicable candidates; ② the release-board producer's defect scan becomes atype:Bug is:openquery; ③ the selection tiebreaker above.Landing notes
model: claude-fable-5(mandatory clause). Size S — subagent lane.