roadmap▌

Expert strategist managing project roadmaps and strategic direction. Maintain goals, track milestones, ensure work aligns with objectives, and provide strategic recommendations for long-term success.

Generate a comprehensive technical roadmap for building an entire application. Detailed enough that Claude Code can pick up any phase and execute it autonomously for hours.

A technical roadmap provides a strategic plan for technology evolution, guiding architectural decisions, infrastructure investments, and capability development aligned with business objectives.

You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Strategic product roadmap planning using RICE, MoSCoW, ICE, and dependency mapping frameworks. \n \n Supports multiple roadmap formats: Now/Next/Later for simplicity, Quarterly Themes for strategic alignment, OKR-aligned roadmaps for accountability, and Gantt views for execution planning \n Includes four prioritization frameworks (RICE scoring, MoSCoW categorization, ICE scoring, and Value vs Effort matrices) to defend prioritization decisions across different contexts \n Provides dependency map

Transform strategy into a sequenced, outcome-driven roadmap that aligns stakeholders and guides execution. \n \n Orchestrates five phases over 1-2 weeks: gather inputs (business goals, customer problems, technical constraints), define epics with hypotheses and success metrics, prioritize using frameworks like RICE, sequence by quarter with dependency mapping, and communicate with strategic narrative \n Emphasizes outcome-driven epics over feature lists, with each initiative tied to business metr

Framework-driven approach to sequencing features and allocating resources across competing priorities. \n \n Draws on 75 product leaders' frameworks including \"cannonballs vs. lead bullets\" (80/20 balance of big bets and incremental work), \"seasons\" for fast-changing markets, and growth models as common currency for cross-team comparison \n Emphasizes separating conviction from hypothesis, challenging assumptions about impact, and using roadmaps as feasibility checks rather than commitments