beads-priority-assignment

Assign priorities to Beads issues by evaluating urgency, impact, and risk. This process uses a scoring rubric to map these factors into appropriate priority levels like P0–P4, numeric, or named values for effective task prioritization.

Triage tasks in Beads by applying a structured priority assignment rubric. It scores issue urgency, impact, and risk to determine the correct priority level, ensuring work is organized and executed efficiently during the triage process.

Default priority assignments are available for Beads issues with no clear signal. When creating or triaging an issue and urgency or impact is ambiguous, the system provides default priority values to ensure the task is handled appropriately.

The Beads CLI is required to assign priority values. You use the command line interface to create issues and set priorities, for example by passing the desired priority value through the `--priority` flag during issue creation.

Create a Beads task with a specific priority using the command line. Execute `bd create --type task --title "..." --repo <repo> --priority <value>` to instantly assign the correct priority level to your new issue.

Supported priority levels for Beads work management include P0–P4, numeric, and named values. These levels are determined by scoring urgency, impact, and risk to organize and execute work based on issue severity.