This skill discovers product ideas, customer feedback, market trends, and competitor features from various connected sources like CRM, support tickets, analytics, and market research tools. It then produces a dynamically prioritized feature backlog and a living product roadmap, complete with estimated impact, effort, and strategic alignment. The skill verifies prioritization decisions against defined business objectives, available data, and chosen prioritization frameworks. This ensures the roadmap is data-informed and strategically sound. It keeps the roadmap current by continuously monitoring new incoming data and automatically re-evaluating priorities, never inventing unverified details and clearly marking any assumptions or unconfirmed data points for human review.
This skill discovers product ideas, customer feedback, market trends, and competitor features from various connected sources like CRM, support tickets, analytics, and market research tools. It then produces a dynamically prioritized feature backlog and a living product roadmap, complete with estimated impact, effort, and strategic alignment. The skill verifies prioritization decisions against defined business objectives, available data, and chosen prioritization frameworks. This ensures the roadmap is data-informed and strategically sound. It keeps the roadmap current by continuously monitoring new incoming data and automatically re-evaluating priorities, never inventing unverified details and clearly marking any assumptions or unconfirmed data points for human review.
Product teams face the recurring pain of subjective and inconsistent feature prioritization, leading to wasted development effort on low-impact features and missed market opportunities. This often results from a lack of consolidated data, bias in decision-making, or an inability to quickly adapt to changing market conditions.
The real cost includes delayed time-to-market for critical features, low customer satisfaction due to misaligned product development, and inefficient resource allocation across engineering teams. These issues directly hinder scalable business growth and competitive advantage.
This skill removes the manual, often biased, and time-consuming process of prioritization by providing a data-driven, continuously updated roadmap. It frees product managers to focus on execution, stakeholder communication, and strategic thinking, rather than constant data gathering and re-prioritization.
Product managers, product owners, and engineering leads in software companies, startups, and enterprise product divisions.
Especially valuable when:
This skill replaces countless hours of manual data gathering, analysis, and debate that product teams typically spend on feature prioritization. It automates the synthesis of customer feedback, market trends, and internal data, freeing product managers to focus on strategic execution rather than administrative overhead.
The value compounds over time as the skill continuously monitors new information, automatically re-evaluating priorities and keeping your roadmap current. This ensures your product remains aligned with market needs and business objectives, preventing costly missteps and maximizing development ROI.
Beyond generated text, you are paying for a sophisticated, always-on product strategy assistant. It provides a verifiable, data-backed framework for decision-making, reduces subjective bias, and offers a transparent justification for every roadmap item, fostering stakeholder confidence and alignment.
One payment, yours permanently. Download it again at any time and get later versions free.
While product-manager-toolkit offers general tools and market-sizing-analysis provides market data, this skill performs the specific operational job of integrating diverse data streams to dynamically prioritize features and generate a living product roadmap. It constantly adapts to new information, acting as an active prioritization and roadmap generation engine, rather than just a static report or a collection of templates.
The situation it solves: Product teams face the recurring pain of subjective and inconsistent feature prioritization, leading to wasted development effort on low-impact features and missed market opportunities. This often results from a lack of consolidated data, bias in decision-making, or an inability to quickly adapt to changing market conditions.
- When launching a new product and needing an initial, validated roadmap based on early market signals.
- When managing a rapidly evolving product with a constant influx of new feature requests and changing priorities.
- When struggling to align development efforts effectively with overarching strategic business goals.
- When needing to justify feature decisions with objective, data-backed evidence to internal and external stakeholders.
- When dealing with a large, unprioritized backlog of ideas that is overwhelming the product team.
Access Credentials: Credentials for CRM, support, analytics, and market research platforms.
Strategic Business Objectives: Clearly defined, measurable business goals the product roadmap should support.
Prioritization Framework: The chosen framework (e.g., RICE, MoSCoW) and its specific definitions/scoring guidelines.
Development Team Capacity: Estimated capacity of the development team for upcoming periods.
Prioritized Feature Backlog: A list of features ranked by priority, including estimated impact and effort.
Dynamic Product Roadmap: A visual representation of the product roadmap with timelines, dependencies, and justifications.
Prioritization Justification Report: A detailed report explaining the data, framework, assumptions, and trade-offs behind the prioritization decisions.
Connect to specified CRM, support, analytics, and market research platforms using provided credentials.
Done when: All specified data sources are successfully connected and accessible.
If it cannot finish: Report specific connection failure, log the incident, and proceed with available data, clearly noting the missing input.
Extract all unprioritized product ideas, feature requests, customer feedback, market trends, and competitor offerings from connected sources.
Done when: All product ideas, feature requests, customer feedback, market trends, and competitor offerings are extracted and categorized.
If it cannot finish: Flag any inaccessible data sources and continue processing with available data, noting the gap.
Establish clear, measurable strategic business objectives and explicit definitions/scoring guidelines for the chosen prioritization framework (e.g., RICE, MoSCoW).
Done when: Strategic business objectives are clearly defined, and the chosen prioritization framework has explicit, agreed-upon definitions for its components.
If it cannot finish: Prompt the user for missing business objectives or framework definitions, pausing until provided.
Estimate potential business impact for each feature, linking it to SMART objectives, and gather preliminary development effort estimates from engineering.
Done when: Each feature has an estimated business impact (linked to SMART objectives) and a preliminary development effort estimate from engineering.
If it cannot finish: If effort estimates are missing or incomplete, prompt the user for input or use default assumptions, clearly stating them in the output.
Apply the chosen prioritization framework to generate a prioritized feature backlog and construct a dynamic product roadmap with timelines and dependencies.
Done when: A dynamically prioritized feature backlog and a living product roadmap with timelines and dependencies are generated.
If it cannot finish: If prioritization logic encounters inconsistencies, flag conflicting data points for human review and suggest reconciliation strategies.
Check the generated roadmap for internal consistency, feasibility within development capacity, alignment with strategic business objectives, and transparently mark all assumptions.
Done when: The generated roadmap is verified for internal consistency, feasibility within capacity, alignment with strategic objectives, and all assumptions are clearly marked.
If it cannot finish: Identify specific inconsistencies (e.g., over-capacity, misaligned feature), report them, and suggest adjustments for user review.
Prepare a comprehensive roadmap presentation detailing the key data points, the applied prioritization framework, strategic objectives addressed, and any significant assumptions or trade-offs.
Done when: A comprehensive roadmap presentation is prepared, detailing data points, framework, objectives, and trade-offs.
If it cannot finish: If critical justification data is missing, flag it and request user input before finalizing the presentation.
Continuously monitor incoming customer feedback, market data, and product usage analytics for significant changes.
Done when: A continuous monitoring system is active, flagging significant changes in customer feedback, market trends, or competitive landscape, triggering re-evaluation.
If it cannot finish: If the monitoring system fails, alert the user and log the incident, recommending manual checks until restored.
| The mistake | What it costs | How the skill prevents it |
|---|---|---|
| Prioritizing features based solely on internal stakeholder requests without validating against external customer data or market demand. | Development resources are allocated to features that solve internal problems or personal preferences, leading to low customer adoption, wasted effort, and missed market opportunities. | Require that every high-priority feature has supporting evidence from at least two external data sources, such as customer interviews, usage analytics, or market research, before it is placed on the roadmap. |
| Generating a roadmap that is technically unfeasible or exceeds the development team's capacity. | The roadmap becomes an aspirational document rather than an actionable plan, leading to constant delays, missed commitments, team burnout, and a loss of trust with stakeholders. | Mandate that all features on the roadmap include a preliminary effort estimate from engineering and that the total estimated effort for any given period does not exceed 80% of the known team capacity. |
| Using a prioritization framework, such as RICE or MoSCoW, inconsistently or without clear, agreed-upon definitions for its components. | Prioritization scores become arbitrary and indefensible, leading to subjective debates, a lack of transparency, and an inability to objectively compare feature value. | Before prioritization, require explicit definitions and scoring guidelines for each component of the chosen framework, ensuring all team members apply them uniformly, and verify consistency through spot checks. |
| Failing to establish clear, measurable business objectives against which feature impact can be assessed. | Features are developed without a clear understanding of their intended value, making it impossible to measure success, learn from outcomes, or justify investment. | Insist that every feature considered for the roadmap is linked to at least one specific, measurable, achievable, relevant, and time-bound (SMART) business objective. |
| Allowing the roadmap to become static, failing to adapt to new information or changing market conditions. | The product loses relevance, competitive advantage erodes, and development efforts continue on features that are no longer optimal, leading to significant opportunity costs. | Implement a continuous monitoring system that automatically flags significant changes in customer feedback, market trends, or competitive landscape, triggering a mandatory re-evaluation of relevant roadmap items. |
| Presenting a roadmap to stakeholders without transparently explaining the data, assumptions, and trade-offs behind the prioritization decisions. | Stakeholders lack confidence in the product direction, leading to constant challenges, re-litigation of decisions, and difficulty securing necessary resources or buy-in. | Require that every roadmap presentation includes a dedicated section detailing the key data points, the prioritization framework applied, the strategic objectives addressed, and any significant assumptions or trade-offs made. |
A SaaS company, 'InnovateCo', wants to prioritize features for its Q3 product roadmap. They have customer feedback in Zendesk, usage data in Mixpanel, and market research reports. Their strategic objective is to 'Increase user engagement by 15% by end of Q3'. They use the RICE framework.
{"Access Credentials": {"zendesk": {"api_key": "abc"}, "mixpanel": {"project_token": "123"}, "market_research_tool": {"auth_token": "def"}}, "Strategic Business Objectives": ["Increase user engagement by 15% by end of Q3", "Reduce churn by 5% in Q3"], "Prioritization Framework": {"name": "RICE", "reach_definition": "Number of active users impacted per month", "impact_scale": "1 (minimal) to 5 (massive)", "confidence_scale": "1 (low) to 100 (high) percent", "effort_scale": "1 (days) to 10 (months)"}, "Development Team Capacity": {"Q3": "100 story points"}}{"prioritized_backlog": [{"feature": "In-app tutorial for new users", "RICE_score": 250, "impact": "High", "effort": "Medium"}, {"feature": "Advanced analytics dashboard", "RICE_score": 180, "impact": "Medium", "effort": "High"}, {"feature": "Integrate with Slack for notifications", "RICE_score": 120, "impact": "Medium", "effort": "Medium"}, {"feature": "Customizable reporting module", "RICE_score": 90, "impact": "Low", "effort": "High"}], "roadmap_summary": "Q3 roadmap focuses on user engagement and onboarding. Key features: In-app tutorial (July), Slack integration (August), Advanced analytics (September). Customizable reporting deferred to Q4 due to lower RICE score and high effort.", "justification_report_excerpt": "The 'In-app tutorial' feature scored highest (RICE: 250) due to high reach (all new users), high impact on engagement (customer feedback indicates onboarding friction), and medium effort. It directly supports the 'Increase user engagement' objective. Development effort for 'Advanced analytics dashboard' is high, pushing it later in Q3, despite medium impact. All effort estimates provided by engineering lead. Assumptions: 1.5x increase in tutorial completion leads to 5% increase in 30-day retention."}Why this output: The output prioritizes features based on the RICE framework, aligning with the 'Increase user engagement' objective. The 'In-app tutorial' is prioritized first due to its high RICE score, directly addressing customer feedback on onboarding. Features with lower scores or higher effort are placed later or deferred, ensuring the roadmap fits within the Q3 capacity. The justification report transparently explains the scores, data sources, and assumptions, addressing potential stakeholder questions.
Continuously monitors incoming customer feedback, market data, and product usage analytics, automatically re-running the prioritization engine and suggesting updates to the product roadmap as new information becomes available, ensuring its ongoing relevance.
Copy SKILL.md to your skills directoryIt connects to your CRM, analytics, and market research tools to gather real-time data on customer feedback, usage patterns, and market trends. All prioritization decisions are explicitly linked to this verifiable data and defined business objectives.
While it generates the roadmap and backlog, direct integration for task management is not within its scope. You can export the prioritized backlog and roadmap summary to import into your project management system.
The skill is designed for continuous adaptation. If your strategic objectives are updated, you can re-run the prioritization process with the new objectives, and the roadmap will be re-evaluated and adjusted accordingly.
No, the skill explicitly states it will not invent any unverified details. All product ideas, customer feedback, and market data must come from connected, verifiable sources or be provided by the user. Any assumptions are clearly marked.
No ratings yet. If you have used this skill, yours would be the first.
Sign in to leave a rating
An account keeps your review with your name on it, and lets you edit it later. Sign in or create one free.
No reviews yet
This skill has not been rated. If you have run it, a short note about what you used it for helps the next person more than any description can.
Discover more AI agent skills in the same category to enhance your workflow automation.
Automatically monitors project execution, identifies deviations from the plan, predicts potential risks.
Automatically drafts, refines, and distributes relevant meeting agendas based on context, ensuring productive discussions.
Expert in building and selling Notion templates as a sustainable digital product business, covering design, pricing, marketing, and scaling for real revenue.
Automate Monday.com workflows including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio).
Interact with Azure Data Lake Storage Gen2 using Python for hierarchical file systems, big data analytics, and file/directory operations.
Enables real-time, bidirectional voice conversations with AI assistants in Java applications using the Azure AI VoiceLive SDK and WebSocket technology.
Join the community and help AI agents learn new capabilities. Submit your skill and reach thousands of developers.