prioritize

Featured

Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.

AI & Automation 948 stars 104 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
64
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# prioritize <!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. --> ## Purpose Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals. Before investigating or acting: 1. Read [the task context contract](references/task-context.md). 2. Read [the method](references/pick-three.md). Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required. ## Principles - Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound. - If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered. - The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance. - Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.

Details

Author
suboss87
Repository
suboss87/FDEOps
Created
3 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

options

Compare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.

948 Updated yesterday
suboss87
AI & Automation Listed

choosing-tools

Decide which installed skill or tool, if any, should own a task — a fit-ranking dispatch step at task starts and direction changes, not a per-message ritual. Use when starting substantive work that more than one installed capability could plausibly own, when unsure whether a discipline skill (TDD, debugging, data-contract guardrails) applies to the work at hand, when two skills seem to claim the same job, or when the user asks "which tool/skill should handle this". Ranks candidates against their descriptions' positive and negative triggers and loads one only when its expected benefit clearly exceeds its context and anchoring cost; exits in one line when nothing fits, and sets aside a loaded skill plainly when it turns out wrong. Pairs with toolkit-awareness, which answers what is installed — this skill decides whether and when to load it. Not for inventory questions (that is toolkit-awareness) and not for authoring or tuning skill descriptions (that is skill-authoring).

2 Updated 6 days ago
grimaldost
AI & Automation Solid

prioritize

Score and rank features, ideas, or bets and produce a defensible ranked list plus a clear recommendation. Use when the user wants to prioritize these features, decide what to build first, RICE score this backlog, rank these ideas, run a value vs effort 2x2, or pick the right prioritization framework. Picks the framework, defines the scale, scores consistently, and surfaces the close calls.

6 Updated 3 weeks ago
Sidsaladi9