Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill whenever you bd create a issue or re-triage priority (bd update) so the queue reflects real severity. Follow bd doctor / your Beads version for the exact --priority values your CLI accepts (integers 0–4, labels like P0–P4, and/or names like critical / high / medium / low).
types/beads.ts)Exports and the dashboard normalize numeric priority roughly as:
| Tier | Typical bd inputs | Meaning in this harness |
|---|---|---|
| Critical | 0, P0, critical | Drop other work: production down, active exploit, data loss, irreversible customer harm |
| High | 1, P1, high | Urgent: broken main path, release blocker, failing CI on default branch, severe bug with weak workaround |
| Medium | 2, P2, medium | Default scheduled work: most features, typical bugs, refactors with agreed dates |
| Low | 3–4, P3–P4, low | Backlog: polish, nice-to-have, cleanup, research spikes with no near deadline |
Values 3 and above both map to low in the static dashboard export — use them to order work inside the backlog if your bd install preserves numeric order.
Score mentally; the highest axis that applies usually wins (then downgrade one step if mitigations exist).
Escalate one level if the issue blocks other ready work or sits on a critical path to a dated epic.
De-escalate one level if there is a documented workaround, the area is feature-flagged off, or the report is duplicate / unclear until clarified.
P2 / 2 / medium (harness default), not empty priority.| Situation | Suggested priority |
|---|---|
| Auth service returning 500 for all logins | 0 / P0 / critical |
CI red on master, no merge until fixed | 1 / P1 / high |
| New feature from roadmap, normal sprint | 2 / P2 / medium |
| Typo in internal-only docs | 3 or 4 / low |
/triage auto-filed “CI failing on PR #n” (matches existing harness command) | 1 / P1 / high |
bd create --type task --title "[<repo>] ..." --priority <value>
bd update <id> --priority <value>
After changing priority on an existing issue, add a short Beads comment: worklog: priority set to <value> because <one line>.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Capture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.
The English summary is being prepared. Showing the original description.
Register a new sub-repo in the knowledge base.
The English summary is being prepared. Showing the original description.
Add focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.
The English summary is being prepared. Showing the original description.
Answer questions about the codebase from knowledge files. Use when the user runs /ask or asks a domain/knowledge question about the repos.
The English summary is being prepared. Showing the original description.
Meta-skill for creating Agent Forge skills under .claude/skills/ with SKILL.md, optional references/ and scripts/, and Bun scaffolds. Use when the user wants to add or author a skill, scaffold a new skill folder, or align skill docs with harness conventions (JSON script output, Beads for tasks).
The English summary is being prepared. Showing the original description.
Ultra-compressed communication mode that preserves technical accuracy while dropping filler. Use when the user explicitly says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
The English summary is being prepared. Showing the original description.