roadmap-planning

Generate outcome-based roadmaps using the Now/Next/Later framework.

54|4|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/assimovt/productskills --skill roadmap-planning-assimovt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/assimovt/productskills/tree/main/skills/roadmap-planning
Command: npx skills add https://github.com/assimovt/productskills --skill roadmap-planning-assimovt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create outcome-based roadmaps that focus on problems to solve and value to deliver, rather than feature lists and arbitrary dates.

Core Features & Use Cases

  • Outcome-Oriented Planning: Organizes work around achieving specific results.
  • Now/Next/Later Framework: Provides clear horizons for committed, shaped, and exploratory work.
  • Shape Up Integration: Aligns with cycle-based planning and betting.
  • Use Case: When asked to plan the next quarter's initiatives, use this Skill to define key outcomes like "Reduce user onboarding drop-off by 15%" instead of listing features.

Quick Start

Use the roadmap-planning skill to create a Now/Next/Later roadmap for the upcoming quarter.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I create an outcome-based roadmap instead of a feature list?

To create an outcome-based roadmap, organize work around achieving specific results like reducing drop-off rates, rather than listing features. This approach prioritizes problems to solve and value to deliver over arbitrary dates.

What is the Now Next Later framework for product planning?

The Now Next Later framework structures product planning into clear horizons for committed, shaped, and exploratory work. It replaces rigid Gantt charts by focusing on priorities and outcomes rather than fixed timelines.

How do I plan a product roadmap using Shape Up principles?

Plan a product roadmap using Shape Up principles by aligning cycle-based planning with outcome definitions. This involves categorizing work into shaped, committed, or exploratory tracks and avoiding fixed dates beyond a six-week cycle.

Can I use outcome-based roadmaps for quarterly product strategy planning?

Yes, you can use outcome-based roadmaps for quarterly product strategy planning. By defining key outcomes and statuses for each item, teams can map committed and exploratory work without relying on arbitrary feature delivery dates.

Why should I avoid fixed dates in product roadmap planning?

You should avoid fixed dates in roadmap planning beyond six weeks because development cycles are unpredictable. Focusing on outcomes and the Now Next Later framework allows teams to adapt to changing priorities without committing to unrealistic timelines.

What do I need to define before creating a Now Next Later roadmap?

Before creating a Now Next Later roadmap, you need to clearly define the outcomes, supporting evidence, and current status for each item. This ensures the roadmap prioritizes problem-solving over feature delivery.