roadmap-builder

Prioritizes product roadmap features using an effort-impact scoring matrix.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AIBPM42/hodgesfooshee-site-spark --skill roadmap-builder-aibpm42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-builder
Source: https://github.com/AIBPM42/hodgesfooshee-site-spark/tree/main/.claude/skills/roadmap-builder
Command: npx skills add https://github.com/AIBPM42/hodgesfooshee-site-spark --skill roadmap-builder-aibpm42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle with feature creep, misprioritization, and building for imaginary users, leading to wasted development effort and delayed launches. This skill provides a clear framework to focus your product roadmap.

Core Features & Use Cases

  • Impact vs. Effort Prioritization: Evaluates features based on their potential impact on core metrics versus the engineering effort required, ensuring high-value work is prioritized.
  • Stage-Based Rules: Applies specific rules for pre-launch, post-launch, and growth phases, ensuring features align with the product's current lifecycle.
  • Feature Validation Framework: Guides users through critical questions to validate demand, identify underlying problems, and avoid building features nobody truly needs.
  • Use Case: You're in the 'Pre-Launch Stage' and considering adding an analytics dashboard. Use this skill to determine if it's a core loop feature or if it should be deferred, keeping you focused on shipping your MVP.

Quick Start

Use the roadmap-builder skill to help me prioritize features for my new 'social media scheduling app'.

Frequently Asked Questions about roadmap-builder

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

FAQPage Schema
How do I prioritize features for my product roadmap?

Prioritize features by evaluating impact versus effort required. This framework scores each feature on its potential effect on core metrics and engineering cost, ensuring high-value work gets built first and low-impact work gets deferred or rejected.

What's the best way to avoid building features nobody needs?

Validate feature demand before prioritizing. This skill guides you through critical questions to identify underlying problems, confirm user need, and measure expected impact, preventing wasted development effort on features with insufficient demand.

How do I apply different prioritization rules at different product stages?

Apply stage-specific rules for pre-launch, post-launch, and growth phases. Each stage has distinct priorities—pre-launch focuses on core loop features, post-launch on retention, growth on monetization—ensuring your roadmap aligns with your product lifecycle.

Can I use this framework to challenge feature requests and backlog decisions?

Yes. This skill provides a decision workflow and validation checks to evaluate incoming requests against strategic bets and measurable impact criteria, helping you say no to misaligned features and stay focused on core use cases.

Does this approach work for deciding what to build in an MVP?

Yes. The framework includes pre-launch rules and impact-versus-effort scoring to identify which features are essential for MVP launch versus deferred post-launch, helping you ship faster with purposeful prioritization.

What categories should I use to organize my feature backlog?

Organize features into a category hierarchy: Retention, Core Features, Monetization, and Growth. This hierarchy guides stage-specific prioritization, ensuring early-stage products focus on retention and core loops before pursuing monetization or growth features.