prioritize
Score and rank features or initiatives so teams build the highest-value things first.
Step 1: Gather the List
Collect the items to prioritize. If the user hasn't provided them, ask. Each item needs a clear, concise name and a one-sentence description of what it delivers.
Don't prioritize fewer than 3 items (just pick the best one) or more than 25 (split into themes first, then prioritize within each).
Step 2: Choose a Framework
Pick one based on what the team actually has available:
| If you have... | Use | Why |
|---|---|---|
| Usage data, reach estimates, engineering sizing | RICE | Rigorous, accounts for confidence in your estimates |
| JTBD need statements with importance/satisfaction data | Opportunity scoring | Finds underserved needs directly |
| A large list and need a quick first pass | Impact/Effort matrix | Fast triage, no math required |
| Limited data but reasonable intuition | ICE | Lighter-weight RICE, moves fast |
More from kazdenc/builder-skills
design-brief
One-time setup that gathers design context for your project and saves it to your config file. Run once to establish persistent design guidelines.
31prd
Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and edge cases. Use when user says "write a PRD", "product requirements", "requirements doc", "spec this feature", "document requirements", or needs to define what to build and why.
17critique
Evaluate design effectiveness from a UX perspective. Use when user says "critique this design", "review the UX", "give design feedback", "is this good design", "design review", "evaluate this layout", or wants expert evaluative feedback on visual hierarchy, information architecture, and emotional resonance.
14security-scan
Check code for OWASP top 10 vulnerabilities including injection, XSS, auth issues, and secrets exposure. Use when user says "security audit", "check for vulnerabilities", "security scan", "is this secure", "OWASP check", "find security issues", or needs to verify code security before shipping.
13polish
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues. Use when user says "polish this", "final pass", "ready to ship", "fix the details", "pixel-perfect", "almost done", or when a feature is functionally complete but needs refinement.
13env-config
Set up environment variables across local, staging, and production with validation and documentation. Use when user says "set up env vars", "environment variables", "configure secrets", ".env setup", "env validation", or needs to manage configuration across environments.
12