decide-priority

Ranks concrete work items and defines revisit triggers for parked tasks.

Updated Jul 3, 2026

Search Tags:#decision making #prioritization #backlog #work items #defer #revisit trigger #task ranking

One-click install

npx skills add https://github.com/mnazaal/dotfiles --skill decide-priority-mnazaal

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: decide-priority
Source: https://github.com/mnazaal/dotfiles/tree/main/.agents/skills/decide-priority
Command: npx skills add https://github.com/mnazaal/dotfiles --skill decide-priority-mnazaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often stall when choosing which task to do next, or they "park" work items without ever defining when to revisit them, leaving abandoned tasks that still look alive. This Skill structures priority decisions so every deferral includes an explicit revisit trigger. ## Core Features & Use Cases - Work Item Ranking: Decide which concrete task to tackle next, or whether to rollback, defer, or continue current work. - Parking with Revisit Triggers: Ensures every parked item states, in the user's own words, what condition would bring it back. - Meaningful Option Labels: Keeps the user's names for options in scoring tables instead of opaque labels like P0 or Option A. - Use Case: You have five competing bug fixes and features. Use this Skill to rank them, pick the next task, and record exactly what signal would revive the deferred items. ## Quick Start Help me decide which of these tasks to work on next and what to park, with a revisit trigger for each parked item.

Frequently Asked Questions about decide-priority

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why avoid labels like P0 or Option A in scoring tables?▼

Generic labels strip away meaning, making rows unreadable on their own and hiding the real trade-offs. Keeping the user's names for options ensures each scoring-table row is meaningful alone.