outcome-roadmap

The outcome-roadmap skill transforms an output-focused roadmap, which emphasizes features, into an outcome-focused one that communicates strategic intent by rewriting initiatives as outcome statements reflecting user and business impact. It solves the problem that output-focused roadmaps create false precision and misalign teams around features rather than results, whereas outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking. It is intended for shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes for the subject supplied via $ARGUMENTS.

The skill guides the assistant to gather the current roadmap and, if strategy documents or company objectives are mentioned, to use web search to understand alignment with broader goals. It then thinks step by step for each initiative, asking what outcome is being pursued, what customer problem is being solved, and what business metric will improve. Its transformation process identifies the output, uncovers the outcome, and rewrites each initiative using the format "Enable [customer segment] to [desired customer outcome] so that [business impact]." A worked example converts a Q2 feature list (advanced search filters, AI recommendations, dashboard redesign) into measurable outcome statements such as finding products 50% faster or increasing average order value by 20%. The output is structured with original initiatives by quarter, outcome statements, key success metrics, and dependencies, plus strategic context on alignment, assumptions, and flexible release windows.

This skill targets product managers and leaders who want more strategic, resilient roadmaps. It advises that outcomes be testable and measurable, that multiple outputs may achieve one outcome, and that when unsure what outcome a feature drives, one should keep asking "So what?" until reaching real customer or business value. If the result is substantial, it saves the output as a markdown document named Outcome-Roadmap-[year].md, and it links to further reading on product vision, OKRs, and outcome types.