From 1d6ec89f6a547449c01e17d03e44689433db27f7 Mon Sep 17 00:00:00 2001 From: Cristian Magherusan-Stanciu Date: Fri, 16 Oct 2026 22:18:06 +0200 Subject: [PATCH] docs(claude): spell out the issue priority order Step 1 of the issue-assignment section said only "highest priority, oldest first". Spell out the full order agents use: priority/p0 through p3, then unlabelled; within a level urgency, impact, unblocking and smaller effort; oldest as the final tie-break; and skip blocked, needs-info, wontdo, assigned, claimed or already-PR'd issues. Matches the platform and mcp repos. 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 c15cc4ad4..cf3518b50 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -75,8 +75,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