- Home
- Skills
- Product Management
- feature prioritization
Works with the AI Agents you already use
feature prioritization
Managing a product backlog without a clear scoring system leads to subjective decisions and wasted engineering effort.
$1.99
feature prioritization
Example session with this skill installed
Prioritize these features for the Q3 mobile app update:
- Dark Mode (Reach: 5000, Impact: 0.5, Confidence: 1.0, Effort: 1).
- Biometric Auth (Reach: 8000, Impact: 2, Confidence: 0.8, Effort: 3).
- Read your context and instructions
- Compiled the feature prioritization
I have processed the feature candidates for the mobile app update. The scores were calculated using the RICE methodology, and dependencies have been analyzed.
Feature Prioritization — Q3 Mobile App, 2023-10-27
1. Sources and assumptions
- Sources: E1 (User provided feature list)
- Feature Count: 2
- Assumptions:
- Impact values mapped to standard scale (E1, default)
- Effort measured in person-months (E1, user_supplied)
2. Feature rankings
| Rank | ID | Name | RICE Score | Weighted | Status |
|---|---|---|---|---|---|
| 1 | F2 | Biometric Auth | 4266.67 | n/a | needs_review |
| 2 | F1 | Dark Mode | 2500.00 | n/a | completed |
3. RICE score details
| Feature | Reach | Impact | Confidence | Effort | RICE |
|---|---|---|---|---|---|
| Biometric Auth | 8000 | 2.0 | 0.8 | 3.0 | 4266.67 |
| Dark Mode | 5000 | 0.5 | 1.0 | 1.0 | 2500.00 |
4. Dependencies
- Can start immediately: Biometric Auth (F2), Dark Mode (F1)
- Blocked features: None detected.
- Cycles: No cycles detected.
5. Priority backlog (draft)
- Biometric Auth (F2): Ready to start. No blockers.
- Dark Mode (F1): Ready to start. No blockers.
Management decision required — Final backlog prioritization requires product-owner approval.
6. Undefined scores and gaps
All features have valid scores.
7. Warnings and review items
W_REVIEW_REQUIRED: Biometric Auth (F2) requires high implementation effort; verify security requirements.
Next steps
- Review the high-impact score for Biometric Auth with the security team.
- Approve the prioritization for the upcoming sprint planning.
- Add "Push Notifications" if reach estimates become available.
Connects securely to your tools. The creator never sees your data.
About this skill
Managing a product backlog without a clear scoring system leads to subjective decisions and wasted engineering effort. This skill provides a deterministic framework for ranking feature candidates based on RICE (Reach, Impact, Confidence, Effort) and dependency analysis. It eliminates guesswork by using a dedicated execution script to calculate scores and map out blockers.
What it does
- Calculates RICE scores by processing reach, impact, confidence, and effort inputs with exact decimal precision.
- Analyzes dependencies using topological sort to identify which features can start immediately and which are blocked.
- Detects logical cycles in your roadmap to prevent circular dependencies that stall development.
- Identifies information gaps by flagging features with undefined scores or missing input components.
- Generates prioritized backlogs that rank features by value-per-effort while maintaining dependency integrity.
How it works
- Submit your list of feature candidates, including their RICE estimates and any technical dependencies.
- The agent builds a structured request and executes a specialized Python script to perform the arithmetic and sorting.
- Review the generated report which categorizes features by rank, status, and blocking relationships.
Frameworks & tools
This skill utilizes a specialized Python calculation engine for deterministic scoring and topological sorting. It follows the standard RICE methodology (Reach × Impact × Confidence / Effort) and supports weighted scoring models.
Why this beats prompting it yourself
Standard LLM prompts often struggle with multi-step arithmetic and complex dependency chains, leading to "hallucinated" rankings or ignored blockers. This skill offloads the logic to a self-contained script, ensuring the math is always correct and the dependency graph is logically sound.
Use cases
- Validating a messy backlog into a ranked list based on objective reach and impact data.
- Identifying the "critical path" for a product launch by mapping feature dependencies.
- Flagging missing estimates in a roadmap before a high-stakes planning session.
- Comparing features using custom weighted criteria alongside standard RICE scores.
Known limitations
Requires specific RICE components to produce scores; it will not fabricate missing data. It does not handle resource capacity or calendar-based scheduling.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Product Management.
Requires RICE inputs to generate scores. Does not perform calendar-based roadmap scheduling or resource capacity planning. Requires unique feature IDs.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago