roadmap-update

To reprioritize a product roadmap, you describe the new initiative and the Skill adjusts existing priorities, owners, and dependencies to reflect the change. It restructures the roadmap into Now/Next/Later views based on the updated information.

The best way to update product roadmap timelines is providing the delayed item details so the Skill can shift target timeframes and adjust dependencies. This keeps your Now/Next/Later roadmap views accurate without manual timeline recalculation.

Yes, you can create a Now/Next/Later roadmap from a single prompt by providing structured inputs like item names, descriptions, priorities, owners, and target timeframes. The Skill processes these inputs to generate the prioritized roadmap.

To shift roadmap priorities after stakeholder feedback, you need to provide the updated item details including its name, description, new priority level, owner, and dependencies. The Skill uses these structured inputs to reprioritize the product roadmap accordingly.

Yes, this roadmap update approach handles dependencies by accepting them as structured inputs alongside item names and priorities. It factors these dependencies into the prioritization workflow when generating the updated roadmap timeline.

You should use a structured workflow for product roadmap updates when priorities shift frequently or new initiatives arrive, as manual tracking becomes error-prone. It ensures clear alignment and accurate reprioritization across Now/Next/Later views.