From adb8f2980c4c599825583cde05270db27526a566 Mon Sep 17 00:00:00 2001 From: Cristian Magherusan-Stanciu Date: Sat, 17 Oct 2026 14:57:52 +0200 Subject: [PATCH] docs(claude): spell out the issue priority order Step 1 of "Issue assignment" said only "highest-priority, oldest first within a priority". Spell out the full order: p0 through p3 then unlabelled; within a level urgency, impact, unblocks-others and effort; oldest last; and what to skip. Matches platform#947 and mcp#75. The gh query blocks are unchanged. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index b4c39e0a..4b9d6974 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -82,8 +82,11 @@ fixing the same thing. The `~/.claude/agent-comms/` bus below only coordinates agents on one machine; assignment is what coordinates people. 1. **Pick work in priority order.** Take the highest-priority open issue - that nobody owns, oldest first within a priority. Skip anything - labelled `status/blocked`, `status/needs-info` or `status/wontdo`: + that nobody owns: priority/p0 through p3, then no priority label. + Within a level, prefer higher urgency/*, then higher impact/*, then + issues that unblock others, then smaller effort/*. Break remaining ties + oldest first. Skip status/blocked, status/needs-info, status/wontdo, and + anything assigned, claimed or already covered by an open PR. ```bash for p in p0 p1 p2 p3; do