Agent skill · product strategy · borghei
outcome-roadmap
Transform output-based feature lists into outcome-driven Now/Next/Later roadmaps using the "so what?" technique. Use when converting a feature-list roadmap to outcomes, communicating product strategy, or running quarterly planning.
Why this skill is useful
Adds a Python script for transforming feature-based roadmaps into outcome-driven formats, which is not commonly found in public resources.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Outcome Roadmap Expert The agent transforms output-based roadmaps ("build feature X") into outcome-driven roadmaps ("enable customers to achieve Y") using the "so what?" technique and Now/Next/Later framing. It produces roadmaps that communicate strategy and measurable impact, not just feature lists and dates. Core Capabilities Output → outcome transformation — applies the formula "Enable [segment] to [outcome] so that [impact]" via a "so what?" chain that drills from feature to business metric. Now/Next/Later classification — sorts initiatives into horizons whose detail and commitment level match certainty. Metric definition — primary, secondary, and counter-metrics for Now/Next items. Dependency capture — technical, organizational, and market prerequisites per item. Stakeholder-ready output — text, JSON, and markdown reports grouped by horizon for alignment review. When to Use Converting a feature-list / date-driven roadmap into outcome-driven format. Communicating product strategy to executives or customers. Running quarterly planning and aligning teams around impact rather than deliverables. Anchoring roadmap items to customer value and OKRs. Clarify First Before transforming the roadmap, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Customer segment + business impact per item — fills the "Enable [segment] to [outcome] so that [impact]" statement; without it the tool only emits placeholder templates [ ] Target quarter per initiative — drives Now/Next/Later horizon placement and the detail/commitment level [ ] Initiative type — feature / improvement / infrastructure drives the strategic-question and metric suggestions [ ] Success metric per Now/Next item — the primary/secondary/counter-metrics; Later items intentionally stay metric-light to avoid false precision Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/outcome-roadmap