feature-investment-advisor
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill feature-investment-advisorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Product ManagementSupported Platforms
Tags
Our assessment of feature-investment-advisor
feature-investment-advisor scores 86/100 on our quality scale, 42nd of 61 Product Management skills we index.
Its SKILL.md is 22 KB long, well organised into 37 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so feature-investment-advisor is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
feature-investment-advisor compared with similar skills
All 4 of these similar skills score higher than feature-investment-advisor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| feature-investment-advisor (this skill)by deanpeters | 86 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install feature-investment-advisor?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill feature-investment-advisor. The install tabs above show the steps for each supported agent. - Which AI agents does feature-investment-advisor work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is feature-investment-advisor safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is feature-investment-advisor still maintained?
- The repository was last updated about 3 months ago, so feature-investment-advisor is actively maintained.
Skill content
View source on GitHubname: feature-investment-advisor argument-hint: "[feature to evaluate]" description: Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment. intent: >- Guide product managers through evaluating whether to build a feature based on financial impact analysis. Use this to make data-driven prioritization decisions by assessing revenue connection (direct or indirect), cost structure (dev + COGS + OpEx), ROI calculation, and strategic value—then deliver actionable build/don't build recommendations with supporting math. type: interactive best_for:
- "Assessing whether a feature should be built now"
- "Comparing ROI and strategic value of feature ideas"
- "Pressure-testing roadmap requests with financial logic" scenarios:
- "Should we build SSO for mid-market customers this quarter?"
- "Evaluate whether an AI assistant feature is worth the investment"
- "Help me decide if this roadmap request has enough ROI to build" theme: finance-metrics estimated_time: "15-25 min"
Purpose
Guide product managers through evaluating whether to build a feature based on financial impact analysis. Use this to make data-driven prioritization decisions by assessing revenue connection (direct or indirect), cost structure (dev + COGS + OpEx), ROI calculation, and strategic value—then deliver actionable build/don't build recommendations with supporting math.
This is not a generic prioritization framework—it's a financial lens for feature decisions that complements other prioritization methods (RICE, value vs. effort, user research). Use when financial impact is a key decision factor.
Input
Works best with: The feature you're deciding on, in a sentence or two. Also useful: Revenue connection (direct or indirect), rough cost inputs (dev time, COGS, ongoing OpEx), and the strategic argument being made for it.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The advisor opens by asking what the feature is and how it's supposed to make or save money.
Example invocation: Should we build SSO/SAML? Enterprise deals keep stalling on it; est. 2 engineer-months plus ongoing support burden.
Key Concepts
The Feature Investment Framework
A systematic approach to evaluate features financially:
-
Revenue Connection — How does this feature impact revenue?
- Direct monetization (new tier, add-on, usage charges)
- Indirect monetization (retention, conversion, expansion enablement)
-
Cost Structure — What does it cost to build and run?
- Development cost (one-time investment)
- COGS impact (ongoing infrastructure, processing)
- OpEx impact (ongoing support, maintenance)
-
ROI Calculation — Is the return worth the investment?
- Direct monetization: Revenue impact / Development cost
- Retention features: LTV impact across customer base / Development cost
- Factor in gross margin, not just revenue
-
Strategic Value — Non-financial value that might override pure ROI
- Competitive moat (prevents churn to competitor)
- Platform enabler (unlocks future features)
- Market positioning (needed for enterprise deals)
- Risk reduction (compliance, security)
Anti-Patterns (What This Is NOT)
- Not feature scoring alone: Combines financial analysis with strategic judgment
- Not revenue-only thinking: Considers margins, costs, and ROI, not just top-line revenue
- Not ignoring retention: Indirect revenue impact (churn reduction) is equally valid
- Not building without validation: Assumes you've done discovery; this is the financial lens
When to Use This Framework
Use this when:
- Prioritizing between features with quantifiable revenue/retention impact
- Evaluating expensive features (>1 engineer-month of work)
- Making build/buy/partner decisions
- Defending feature prioritization to stakeholders or leadership
- Choosing between direct monetization (add-on) vs. indirect (retention)
Don't use this when:
- Feature is table stakes (must-have for competitive parity)
- Impact is purely qualitative (brand, UX delight without measurable retention effect)
- You haven't validated the problem (do discovery first)
- Feature is < 1 week of work (just build it)
Facilitation Source of Truth
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
- session heads-up + entry mode (Guided, Context dump, Best guess)
- one-question turns with plain-language prompts
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include
Other (specify)when useful)
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
Application
This interactive skill asks up to 4 adaptive questions, offering 3-5 enumerated options at decision points.
Step 0: Gather Context
Agent asks:
"Let's evaluate the financial impact of this feature investment. Please provide:
Feature description:
- What's the feature? (1-2 sentences)
- Target customer segment (SMB, mid-market, enterprise, all)
Current business context:
- Current MRR/ARR (or customer count if pre-revenue)
- Current ARPU/ARPA
- Current monthly churn rate
- Gross margin %
Constraints:
- Development cost estimate (team size × time)
- Any ongoing COGS or OpEx implications?
You can provide estimates if you don't have exact numbers."
Step 1: Identify Revenue Connection
Agent asks:
"How does this feature impact revenue? Choose the option that best describes the revenue connection:
- Direct monetization (new revenue stream) — We'll charge for this (new pricing tier, paid add-on, usage-based fee)
- Retention improvement (reduce churn) — Addresses key churn reason; keeps customers from leaving
- Conversion improvement (trial-to-paid) — Helps convert free/trial users to paid customers
- Expansion enabler (upsell/cross-sell) — Creates upsell path or drives usage-based expansion
- No direct revenue impact — Table stakes, platform improvement, or strategic value only
Choose a number, or describe a custom revenue connection."
Based on selection, agent adapts:
If 1 (Direct monetization):
- "What pricing are you considering?"
- "What % of customers do you expect to adopt this?" (conservative, base, optimistic)
- Calculate:
Potential Monthly Revenue = Customer Base × Adoption Rate × Price
If 2 (Retention improvement):
- "What % of churn does this feature address?" (e.g., "30% of churned customers cited this gap")
- "What churn reduction do you expect?" (e.g., "5% → 4% monthly churn")
- Calculate:
LTV Impact = Increase in Customer Lifetime × Customer Base × ARPU × Margin
If 3 (Conversion improvement):
- "Current trial-to-paid conversion rate?"
- "Expected conversion lift?" (e.g., "20% → 25% conversion")
- Calculate:
Additional MRR = Trial Users × Conversion Lift × ARPU
If 4 (Expansion enabler):
- "What expansion opportunity does this create?" (upsell tier, usage growth, add-on)
- "What % of customers will expand?"
- Calculate:
Expansion MRR = Customer Base × Expansion Rate × ARPU Increase
If 5 (No direct revenue impact):
- Skip to strategic value assessment
Step 2: Assess Cost Structure
Agent asks:
"What's the cost structure for this feature?
Development cost (one-time):
- Team size: ___ engineers
- Time estimate: ___ weeks/months
- Estimated dev cost: $___
Ongoing costs (if any):
- COGS impact: $___ /month (hosting, infrastructure, processing)
- OpEx impact: $___ /month (support, maintenance)
If no ongoing costs, enter $0."
Agent calculates:
- One-time investment: Development cost
- Ongoing monthly cost: COGS + OpEx
- Contribution margin impact:
(Revenue - COGS) / Revenue
Agent flags:
- If COGS is >20% of projected revenue: "⚠️ This feature significantly dilutes margins"
- If ongoing costs are high relative to revenue: "⚠️ Consider if this is sustainable"
Step 3: Evaluate Constraints and Timing
Agent asks:
"What constraints or timing considerations apply?
- Time-sensitive competitive threat — Competitor launched this; we're losing deals
- Limited budget/team capacity — We can only build one major feature this quarter
- Dependencies on other work — Requires platform improvements or other features first
- No major constraints — We have capacity and flexibility
Choose a number, or describe your constraints."
Based on selection:
If 1 (Competitive threat):
- Strategic value increases (churn prevention)
- Urgency factor in recommendation
If 2 (Limited capacity):
- Compare ROI against other features in backlog
- Recommend stack ranking
If 3 (Dependencies):
- Flag dependency risk
- Suggest sequencing
If 4 (No constraints):
- Proceed to recommendations
Step 4: Deliver Recommendations
Agent synthesizes:
- Revenue impact (from Step 1)
- Cost structure (from Step 2)
- Constraints (from Step 3)
- ROI calculation
- Strategic value assessment
Agent offers 3-4 recommendations:
Recommendation Pattern 1: Strong Financial Case
When:
- ROI >3:1 (direct monetization) or LTV impact >10:1 (retention/expansion)
- Positive contribution margin
- No major red flags
Recommendation:
"Build now — Strong financial case
Revenue Impact:
- [Direct/Indirect revenue impact calculation]
- Conservative estimate: $___/month
- Optimistic estimate: $___/month
Cost:
- Development: $___
- Ongoing COGS/OpEx: $___/month
- Net margin impact: ___%
ROI:
- Year 1 ROI: ___:1
- Payback period: ___ months
Why this makes sense: [Specific reasoning based on numbers]
Next steps:
- Validate pricing/adoption assumptions with customer research
- Build MVP to test core value prop
- Monitor [specific metric] to measure impact"
Recommendation Pattern 2: Weak Financial Case, Build Anyway (Strategic)
When:
- ROI <2:1 or marginal financial impact
- But high strategic value (competitive, platform, compliance)
Recommendation:
"Build for strategic reasons (financial case is marginal)
Financial Reality:
- Revenue impact: $___/month (modest)
- Development cost: $___
- ROI: ___:1 (below 3:1 threshold)
Strategic Value:
- [Competitive moat / Platform enabler / Market requirement]
- Prevents churn to competitor X
- Required for enterprise segment (30% of pipeline)
Recommendation: Build, but monitor closely:
- Track adoption vs. projections
- Measure churn impact (target: reduce churn by ___%)
- Re-evaluate after 6 months if adoption is low
Risk: Opportunity cost—other features may have better ROI"
Recommendation Pattern 3: Don't Build (Poor ROI)
When:
- ROI <1:1 (direct monetization) or negative LTV impact
- Margin-diluting
- No compelling strategic value
Recommendation:
"Don't build — Financial case doesn't support investment
Why:
- Revenue impact: $___/month
- Development cost: $___
- ROI: ___:1 (below breakeven)
- Margin impact: Dilutes gross margin from ___% to ___%
Alternative approaches:
- Reduce scope — Can we build a simpler version at 50% cost?
- Change monetization — Can we charge more or differently?
- Deprioritize — Focus on higher-ROI features like [alternative]
What would need to change:
- If adoption rate increases from ___% to ___%, ROI becomes viable
- If we can reduce dev cost to $___, payback becomes acceptable"
Recommendation Pattern
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
