Yohayetsion Product Org Os Product Roadmap

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete new roadmap using template below.

UPDATE:

1. Read existing roadmap (search if path not provided)
2. Preserve unchanged sections exactly
3. Update specific sections (initiatives, timelines, priorities)
4. Add entry to Change Log section
5. Show diff summary: "Updated: [sections]. Added to changelog."

FIND:

1. Search paths below for roadmaps
2. Present results: title, timeframe, path, date
3. Ask: "Update one of these, or create new?"

Search Locations for Roadmaps

• roadmap/
• strategy/
• planning/
• docs/roadmap/

Gotchas

• Roadmap themes must connect to strategic bets — features without strategic alignment are noise
• Confidence levels decrease with distance — 'Now' is high confidence, 'Later' is directional only
• Never commit to specific dates in the 'Later' horizon — use quarters or 'H2' at most

Create a complete Product Roadmap for the specified timeframe or product area.

Vision to Value Phase

Phase 3: Strategic Commitments - The roadmap is a key commitment artifact that follows strategic decisions.

Prerequisites: Phase 2 complete (business case approved, strategic bets defined) Outputs used by: Phase 3 (PRDs, GTM), Phase 4 (execution tracking)

Output Structure

Generate a comprehensive roadmap document with the following sections:

1. Executive Summary

• Roadmap timeframe
• Key themes and priorities
• Major milestones
• Resource summary

2. Product Vision Alignment

• Company vision reference
• Product vision statement
• How this roadmap advances the vision
• Strategic bets being addressed

3. Strategic Themes

For each theme:

• Theme name
• Strategic rationale
• Customer value
• Business value
• Success metrics
• Investment level (% of capacity)

4. Roadmap View

Now (Current Quarter)

Next (Next Quarter)

Later (Future Quarters)

5. Initiative Details

For each initiative in "Now":

• Description
• Target users
• Success criteria
• Key milestones
• Dependencies
• Risks

6. Dependencies Map

[Visual representation of dependencies between initiatives]

7. Success Metrics by Theme

8. Resource Requirements

• Engineering capacity needed
• Design capacity needed
• Other resources
• Capacity vs demand analysis

9. Risk Assessment

10. Stakeholder Communication Plan

11. Change Log

Instructions

1. Ask about timeframe if not specified (quarterly, annual, etc.)
2. Reference any strategy documents provided via @file syntax
3. Ensure themes connect to strategic goals
4. Include explicit prioritization rationale
5. Save as markdown file
6. Offer to create presentation version using /present

Converted and distributed by TomeVault — claim your Tome and manage your conversions.