omeragaakbas/outcome-roadmap
.claude/skills/outcome-roadmap/SKILL.md
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
documentation
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add omeragaakbas/zoyare outcome-roadmapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 20, 2026, 8:17 AM233.8s1 file scanned
SKILL.md
- name:
- outcome-roadmap
- description:
- Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
Transform Roadmap to Outcome-Focused Format
Purpose
You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.
Context
Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.
Instructions
-
Gather Information: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.
-
Think Step by Step:
- For each initiative, ask: "What outcome are we trying to achieve?"
- What customer problem are we solving?
- What business metric will improve?
- How will this impact the customer experience or business?
- Is there a better, different way to achieve the same outcome?
-
Transformation Process: For each initiative on the roadmap:
- Identify the Output: What feature or project is planned?
- Uncover the Outcome: Why are we building it? What changes for customers or business?
- Rewrite as Outcome Statement: Use this format:
Enable [customer segment] to [desired customer outcome] so that [business impact]
-
Example Transformation:
- Output (Old): Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
- Outcome (New):
- Q2: Enable customers to find products 50% faster through intuitive discovery
- Q2: Increase average order value by 20% through personalized AI recommendations
- Q2: Help operators monitor all systems with 80% reduction in dashboard load time
-
Structure Output: Present the transformed roadmap with:
- Original initiatives listed by quarter/phase
- Outcome statements for each initiative
- Key metrics that will indicate success
- Dependencies or sequencing notes
-
Include Strategic Context: For the overall roadmap, add:
- How outcomes align with company strategy
- Key assumptions about customer needs
- Flexible release windows (quarters, not specific dates)
-
Save the Output: If substantial, save as a markdown document:
Outcome-Roadmap-[year].md
Notes
- An outcome should be testable and measurable
- Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
- Outcome roadmaps are more resilient to change—embrace flexibility
- If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value
Further Reading
- Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition
- Objectives and Key Results (OKRs) 101
- Business Outcomes vs Product Outcomes vs Customer Outcomes
Related Skills
omeragaakbas/product-sense-interview-answer
development
VerifiedTrustedCommunity
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-name
data-ai
VerifiedTrustedCommunity
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/product-marketing-context
development
VerifiedTrustedCommunity
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
SKILL.mdUpdated Apr 17, 2026
omeragaakbas/problem-statement
documentation
VerifiedTrustedCommunity
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.
SKILL.mdUpdated Apr 17, 2026