From 18c56fe1fce57fcbf7583193bdaf1b95040251bb Mon Sep 17 00:00:00 2001 From: Gunju Kim Date: Thu, 26 Feb 2026 22:32:11 +0000 Subject: [PATCH] Complete triage lifecycle with priority, actor, and label cleanup Extend the axon-triage promptTemplate to handle the full triage lifecycle: - Add priority assessment (task 5) with correctly-spelled priority/* labels and clear criteria for each level - Add actor recommendation (task 6) with explicit criteria for actor/axon vs needs-actor - Update label management to swap needs-triage -> triage-accepted after posting the triage comment - Update the triage comment format to include Priority and Actor fields - Rename misspelled GitHub labels (priority/imporant-soon -> priority/important-soon, priority/import-longterm -> priority/important-longterm) Closes #437 Co-Authored-By: Claude Opus 4.6 --- self-development/axon-triage.yaml | 46 +++++++++++++++++++++++++++---- 1 file changed, 41 insertions(+), 5 deletions(-) diff --git a/self-development/axon-triage.yaml b/self-development/axon-triage.yaml index de74ec5..31e4be5 100644 --- a/self-development/axon-triage.yaml +++ b/self-development/axon-triage.yaml @@ -26,8 +26,8 @@ spec: name: axon-dev-agent promptTemplate: | You are a triage agent for the Axon project (github.com/axon-core/axon). - Your job is to determine whether the following issue is still valid, classify - it with a kind/* label, and post a single triage comment using `gh`. + Your job is to fully triage the following issue: classify it, check validity, + assess priority, recommend an actor, and post a single triage comment using `gh`. --- Issue #{{.Number}}: {{.Title}} @@ -74,6 +74,37 @@ spec: Look for semantic overlap, not just title similarity. Flag every duplicate you find with its number and a one-line explanation of why they overlap. + ### 5. Assess priority + Based on your analysis, recommend a priority level: + - `priority/important-soon` — Blocks adoption, user-facing bug, security issue, + or directly requested by the maintainer + - `priority/important-longterm` — Valuable improvement but not urgent, nice-to-have + feature, or quality-of-life enhancement + - `priority/backlog` — Low impact, speculative, or depends on other work + + Apply the label: + `gh issue edit {{.Number}} --add-label --remove-label needs-priority` + + ### 6. Recommend actor + Determine whether this issue can be handled autonomously by Axon's worker agent: + + Assign `actor/axon` if ALL of these are true: + - The issue describes a concrete code change, documentation fix, test improvement, + or configuration update with clear scope + - The acceptance criteria are objectively verifiable (tests pass, docs are accurate, + CLI output matches expectation, etc) + - It does NOT require: new CRD design decisions, breaking API changes, + infrastructure/cluster access, subjective design choices, or external service setup + + Leave `needs-actor` if ANY of these are true: + - The issue requires architectural decisions or community input + - The scope is ambiguous or open-ended + - It depends on external systems Axon cannot access + - It requires human judgment about product direction + + If recommending `actor/axon`: + `gh issue edit {{.Number}} --add-label actor/axon --remove-label needs-actor` + ## Output Post exactly one comment on this issue using: `gh issue comment {{.Number}} --body "..."` @@ -84,6 +115,8 @@ spec: ## Axon Triage Report **Kind**: + **Priority**: — + **Actor**: `actor/axon` or `needs human` — **Status**: STILL VALID / ALREADY FIXED / OUTDATED / DUPLICATE @@ -95,9 +128,12 @@ spec: **Recommendation**: KEEP OPEN / CLOSE (with reason) ``` - After posting the comment, add the `axon/needs-input` label so a maintainer - can review the triage and the issue is not re-processed: - `gh issue edit {{.Number}} --add-label axon/needs-input` + After posting the comment, update labels to complete the triage lifecycle: + `gh issue edit {{.Number}} --add-label triage-accepted --add-label axon/needs-input --remove-label needs-triage` + + The `axon/needs-input` label ensures a maintainer reviews before any worker + agent picks up the issue. The maintainer can override priority or actor + labels, then remove `axon/needs-input` to approve. Do NOT open PRs, push code, or modify any files. Read-only analysis only (except for the comment and labels above).