triage

Issue triage routing uses canonical category and state roles to classify items, progressing them through states like needs-info, ready-for-agent, ready-for-human, or wontfix. This structured workflow ensures consistent execution and reduces cross-team ambiguity.

Preparing an AFK agent brief requires moving an issue to the ready-for-agent state. The workflow gathers context from prior triage notes and reference documents, structuring the data to inform autonomous execution and reduce cross-team drift.

Structuring collaborative issue triage requires enforcing a canonical role model and integrating knowledge bases like AGENT-BRIEF.md and OUT-OF-SCOPE.md. This durable framework documents expected interfaces to guide consistent decision-making and route issues effectively.

Managing issue state transitions from needs-triage to wontfix involves applying a defined state-machine workflow. The process automates routing through needs-info, ready-for-agent, and ready-for-human states, documenting data shapes for consistent execution.

You can use reference documents like OUT-OF-SCOPE.md to enforce scope during issue triage. The workflow integrates these knowledge bases to surface context, informing decisions and ensuring issues align with established boundaries before routing.