prioritiselisted

# /prioritise $ARGUMENTS Rank a list by leverage. Aristotle is the engine. This skill is the focused interface - it skips the full 5-phase narration and delivers a ranked list with one-line justification per item. **Synergy:** `/aristotle` for deep design decisions (full 5-phase). `/reflection` to identify what ordering improvements to make. When /aristotle is already running, redirect pure ranking requests here instead. ## Parsing args | Input | Action | |-------|--------| | `backlog` / `ideas` | Read the project's IDEAS.md or backlog | | `pending` | Read all open items from the task list | | Inline list (paste items) | Use those items directly | | No args | Ask: "What are you prioritising? Paste your list or name the file." | ## Steps 1. **Load the items.** Read from the named backlog or use inline list. Strip completed and blocked items. Show count: "Ranking N items." 2. **Apply the Aristotle leverage lens** (condensed - no narration): For each item, silently ask: - **Who benefits?** Team-wide > user-only > future-you - **Are they a bottleneck?** Does this unblock other people or other work? - **Irreversibility:** Hard-deadline or drifts-worse-over-time items float up - **Effort vs unlock ratio:** Low-effort items that unblock high-value work > high-effort items with contained value Classify into tiers: - **T1** - multiplier: benefits others or unblocks shared work - **T2** - infrastructure risk: you-only but prevents future pain or has har