What problem does it solve? It removes ambiguity from backlog triage by defining exactly what each type and priority label means, what an issue body must contain, and how ordering constraints are expressed, so triage decisions are made once and read back consistently. ## Core Features & Use Cases - Priority taxonomy: Defines when to apply priority: P0 through P3, plus blocked: design, blocked: dependency, and on hold, based on blocking chains rather than gut feel. - Type labels and label sync: Covers bug, enhancement, documentation, chore, and security, and explains running pnpm repo:labels to sync .github/labels.yml before forms can apply non-default labels. - Issue body requirements: Mandates a path:line for what is wrong and a mechanically checkable close condition, plus the Depends on: #N spelling that automation parses. - Use Case: When re-prioritizing the backlog, use this Skill to decide whether an issue is P0 (an open issue names it as a blocker) or P1 (foundational work future issues build on) instead of tiering by perceived urgency. ## Quick Start Ask the assistant to triage a new GitHub issue for this repository, choosing the correct type and priority label and drafting a compliant issue body.
