roadmap-roast

Evaluate product roadmaps and deliver severity-triaged critiques with market research.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/yp-talia/product-skills --skill roadmap-roast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-roast
Source: https://github.com/yp-talia/product-skills/tree/main/roadmap-roast
Command: npx skills add https://github.com/yp-talia/product-skills --skill roadmap-roast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product leaders and founders turn messy feature lists and delivery schedules into a sharp, evidence-driven critique that reveals sequencing errors, untested assumptions, and market blind spots so teams can prioritise what actually moves the business.

Core Features & Use Cases

  • Self-assessment first: Prompts the user for what feels "shakiest" to surface political or risk areas before analysis.
  • Market-informed critique: Runs targeted web research to name competitors or market signals and integrates that intelligence into the roast.
  • Structured output: Produces a market context, a five-dimension scorecard, a severity-triaged roast (🔴/🟡/🟢), three craft improvements, one concrete thing to do this week, and three specific follow-up threads.
  • Scenario & constraints-aware: Applies user-provided constraints (engineer capacity, committed customers, board dates) and supports debate and scenario reframes.

Quick Start

Ask the assistant: "Roast my roadmap — here are the roadmap items, our company stage, and the six-month success metric" and answer the one self-assessment question when prompted.

Frequently Asked Questions about roadmap-roast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I critique my product roadmap for sequencing errors and market blind spots?

To critique your product roadmap, you need a calibrated evaluation that cross-references your priority list against market context and company stage. This process identifies untested assumptions and sequencing errors by applying targeted web research and a structured five-dimension scorecard to your plan.

What do I need to provide to get a prioritization critique for my feature list?

To get a prioritization critique, you must provide your roadmap items, your current company stage, and a six-month success definition. You should also be ready to answer a self-assessment question about what feels shakiest in your plan to surface political or risk areas.

Can I use a roadmap critique if my team has strict engineer capacity constraints and committed board dates?

Yes, this roadmap critique applies user-provided constraints like engineer capacity, committed customers, and board dates. It integrates these scenario constraints into the analysis and supports debate and scenario reframes based on your specific limitations.

What is the best way to evaluate a product plan against current competitors?

The best way to evaluate a product plan against competitors is to run targeted market research that names specific competitors and market signals. This intelligence is then integrated into a severity-triaged roast to reveal exactly where your sequencing or discovery misses the market context.

How does a severity-triaged roast format help prioritize product improvements?

A severity-triaged roast categorizes roadmap flaws using red, yellow, and green severity levels to help you prioritize product improvements. It pairs this critique with a five-point scorecard, three craft improvements, and one concrete action to execute this week.

Why does roadmap prioritization require a self-assessment step before analysis?

Roadmap prioritization requires a self-assessment step to surface political or risk areas before formal analysis begins. Prompting the user to identify what feels shakiest ensures the final critique addresses internal team doubts and untested assumptions alongside market data.