borghei/Claude-Skills / project-management/execution/outcome-roadmap
outcome-roadmap
VerifiedTurn a feature-list roadmap into outcome statements placed in Now/Next/Later, and check each has a measure. Use when converting a feature-list roadmap, reviewing a roadmap before it goes to leadership, or quarterly planning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.8 KB |
| assets/outcome_roadmap_template.md | markdown | 2.9 KB |
| assets/sample_roadmap.json | config | 1.1 KB |
| assets/sample_roadmap_clean.json | config | 1.6 KB |
| examples/output-to-outcome-transformation.md | markdown | 11.5 KB |
| references/outcome-roadmap-guide.md | markdown | 8.2 KB |
| references/outcome-roadmap-workflow.md | markdown | 8.9 KB |
| references/red-flags.md | markdown | 15.7 KB |
| scripts/roadmap_transformer.py | script | 10.7 KB |
assets/outcome_roadmap_template.md
View on GitHub# Outcome Roadmap: [Product/Team Name]
**Owner:** [Name]
**Last Updated:** [YYYY-MM-DD]
**Strategic Theme:** [One sentence describing the overarching goal for this period]
---
## Now
**Commitment Level:** High -- team assigned, scope defined, work in progress.
### Initiative 1: [Title]
**Outcome Statement:**
> Enable [customer segment] to [desired customer outcome] so that [business impact].
**Success Metrics:**
| Metric | Baseline | Target | Current | Status |
|--------|----------|--------|---------|--------|
| [Leading indicator] | | | | |
| [Lagging indicator] | | | | |
| [Counter-metric] | | | | |
**Team:** [Assigned team or individuals]
**Dependencies:** [What must be true for this to succeed?]
**Strategic Connection:** [How does this connect to company OKRs or strategy?]
### Initiative 2: [Title]
**Outcome Statement:**
> Enable [customer segment] to [desired customer outcome] so that [business impact].
**Success Metrics:**
| Metric | Baseline | Target | Current | Status |
|--------|----------|--------|---------|--------|
| | | | | |
| | | | | |
**Team:**
**Dependencies:**
**Strategic Connection:**
---
## Next
**Commitment Level:** Medium -- direction set, scope flexible, subject to learnings from Now items.
### Initiative 3: [Title]
**Outcome Statement:**
> Enable [customer segment] to [desired customer outcome] so that [business impact].
**Draft Metrics:**
- [Metric 1]
- [Metric 2]
**Open Questions:**
- [ ] [What do we need to learn before committing?]
- [ ] [What dependencies need to be resolved?]
### Initiative 4: [Title]
**Outcome Statement:**
> Enable [customer segment] to [desired customer outcome] so that [business impact].
**Draft Metrics:**
- [Metric 1]
- [Metric 2]
**Open Questions:**
- [ ] [Question]
---
## Later
**Commitment Level:** Low -- strategic intent only, no solution defined.
### Opportunity Area 1: [Problem/Theme]
**Problem Statement:** [What customer or business problem are we considering?]
**Why It Matters:** [Strategic rationale for keeping this on the radar]
**Signals to Watch:** [What would cause us to move this to Next?]
### Opportunity Area 2: [Problem/Theme]
**Problem Statement:**
**Why It Matters:**
**Signals to Watch:**
---
## Initiative Transformation Worksheet
Use this to convert output-based items to outcome-based items.
| # | Original Feature | "So What?" (1) | "So What?" (2) | "So What?" (3) | Outcome Statement |
|---|-----------------|-----------------|-----------------|-----------------|-------------------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
---
## Success Metrics Tracker
| Initiative | Metric | Baseline | Target | Week 1 | Week 2 | Week 3 | Week 4 | Status |
|-----------|--------|----------|--------|--------|--------|--------|--------|--------|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
---
## Change Log
| Date | Change | Rationale |
|------|--------|-----------|
| [YYYY-MM-DD] | [What changed] | [Why] |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |