Flywheel Priority Evaluate
Goal
Ensure every open issue has exactly one priority label aligned with impact and urgency.
Workflow
- •Read
.github/FLYWHEEL.mdand.github/workflows/evaluate.yml. - •List open issues with title, body, and labels.
- •Re-evaluate each issue priority using repository rules:
- •
p0: security/data-loss/blocker - •
p1: important bug/perf/core degradation - •
p2: normal bug/quality/test debt - •
p3: docs/refactor/low urgency
- •
- •Normalize labels so each issue has exactly one of
p0|p1|p2|p3. - •Keep non-priority labels unchanged.
Safety Rules
- •Never remove non-priority labels unless user requests.
- •Never assign multiple priority labels.
- •Default uncertain cases to
p2.
Output Checklist
- •Issues updated with old/new priority
- •Distribution summary by priority