outcome-roadmap takes a roadmap that lists features and rewrites each initiative as an outcome: who is helped, what changes for them and what the business gains. Each line follows the pattern “Enable [customer segment] to [desired outcome] so that [business impact]”.
The result keeps the original initiatives by quarter, adds the outcome statement and the metric that shows success, and closes with strategic alignment, key assumptions and flexible release windows.
What You Get
- A roadmap where every initiative is an outcome statement in the Enable, so that format
- The original initiatives listed by quarter or phase beside their outcomes
- Success metrics for each outcome
- Dependency and sequencing notes
- A strategic context block with alignment to company goals, assumptions about customers and flexible release windows
- A markdown file named Outcome-Roadmap-[year].md when the result is substantial
Common Use Cases
- Rewriting a quarterly feature list before a roadmap review
- Preparing an executive roadmap that shows impact
- Finding the missing why behind items nobody can justify
What Makes It Unique
It pushes every item through the repeated question ‘so what?’ until a real customer or business value appears, and it puts a measurable result on each line. It ships with a worked transformation from three feature items to three metric-backed outcomes, which sets the expected shape of the output.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. The agent reads the roadmap file you provide and may use web search to understand company strategy documents or objectives you mention. It writes the finished roadmap to a markdown file in your working folder when the result is substantial.