pm-roadmap-update

Updating a product roadmap when priorities shift involves capturing current item details, reprioritizing work, and moving timelines while logging why changes matter. This process outputs a scannable summary with grouped items and a before/after change log.

Yes, you can pull current roadmap statuses directly from Linear using Linear MCP integration to establish the baseline. This retrieves existing item details automatically before applying updates, reprioritization, or timeline shifts to your roadmap.

Communicating roadmap changes to stakeholders requires a decision-ready output with a status overview, grouped Now/Next/Later items, risks/dependencies, and a change log. Formatting options tailored for exec or engineering audiences ensure clarity.

Structuring a product roadmap using Now Next Later prioritization involves grouping items by timeframe after collecting their details. This approach creates a scannable summary showing current status, dependencies, and what changed in the latest update.

No, you do not need a specific format to supply current roadmap items for reprioritization. You can provide roadmap details in any format to establish the baseline if you are not integrating with Linear MCP for automatic status retrieval.

Tracking dependencies when adding a new initiative involves collecting item details including name, description, priority, effort, timeframe, owner, and dependencies. The output specifically highlights risks and dependencies alongside the grouped roadmap items.