issue-triage

Assigns structured metadata to GitHub issues (type, priority, effort, duplicates) to enable the DISCUSS phase to refine them in priority order.

When to use

Entry contract

Exit contract

Invariants

Why this shape

Triage establishes a classification discipline before any refinement work. Separating classification (DISCOVER) from refinement (DISCUSS) avoids wasting energy refining low-priority issues or duplicates. The priority decision tree (P0 → P1 → P2 → P3) guarantees consistency across teams.

« Triage is classification, not refinement. You are labeling, prioritizing, and estimating to enable the next phase. »

Duplicate detection via title normalisation (lowercase, stop-word removal, alphabetical sort, overlap ratio) reduces backlog noise without losing the context of original issues.

Allowed customisation

See also