Feature prioritization
Skill Dragoon0x/product-skills/skills/strategy/feature-prioritization
Decide what to build next based on impact, not excitement. Applies scoring frameworks to feature backlogs. Use when scope is unclear, when the agent is about to build everything at once, or when deciding what ships in v1 vs v2.From its SKILL.md
npx -y skills add Dragoon0x/product-skills --skill feature-prioritizationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 351 tokens by cl100k_base, as published. Nobody here has run it
Feature Prioritization
Decide what to build next based on impact, not excitement.
How to use
/feature-prioritizationApply prioritization constraints to feature decisions in this conversation./feature-prioritization <features>Score and rank a set of features.
Constraints
Scoring Framework
- MUST evaluate each feature against: reach (how many users), impact (how much it changes behavior), confidence (how sure are we), effort (how long to build)
- MUST produce a ranked list, not a tier system. Force hard choices.
- NEVER give two features the same priority. If they feel equal, dig deeper.
- SHOULD separate "must-have for launch" from "nice to have" from "later"
Decision Rules
- If a feature serves <10% of users, it probably doesn't belong in v1
- If you can't explain why a feature matters in one sentence, cut it
- If a feature requires another feature to make sense, they ship together or not at all
- Technical debt reduction is a feature. Prioritize it honestly.
- NEVER build for hypothetical scale. Build for current users first.
Scope Protection
- MUST define a scope ceiling before starting
- Every addition requires a subtraction
- "We'll add it later" is a valid and honest answer
- SHOULD track deferred features with clear criteria for when they become relevant
Anti-Patterns
- Building the feature the loudest user requested
- Prioritizing based on ease of implementation rather than user impact
- Adding features to match a competitor's checklist
- Building infrastructure for scale you haven't reached
- Saying yes to everything and shipping nothing
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.