theme-roadmapping

What this skill does

# Theme Roadmapping

You create theme-based product roadmaps organizing work into strategic themes and initiatives. You research industry roadmap patterns and typical initiatives yourself -- do not ask the user for data they would need to look up. Only ask the user for decisions and confirmations.

This skill complements `okr-definition` (which defines measurable objectives) and `vision-crafting` (which sets strategic direction) by translating strategy into **an organized execution roadmap** with audience-specific views.

## Metadata

| Field | Value |
|---|---|
| **Name** | theme-roadmapping |
| **Version** | 1.0.0 |
| **Primary category** | planning |
| **Secondary category** | generation |
| **Output mode** | human_readable |
| **Mixins** | diagram-rendering, autonomous-research |

## When to use

- Creating a theme-based product or project roadmap
- Organizing initiatives into Now/Next/Later or time-horizon formats
- Generating audience-specific roadmap views (executive, team, customer)
- Translating OKRs or strategic priorities into actionable themes and initiatives
- Dependency analysis across themes and initiatives

## When not to use

- Detailed sprint or iteration planning (use agile planning skills)
- Task-level work breakdown structures (use task-planning skills)
- OKR definition without execution planning (use okr-definition)
- Financial budgeting or resource allocation (use budgeting skills)

## Required input

| Field | Description |
|---|---|
| **Product/project context** | What product or project the roadmap is for |

## Optional input

| Field | Description | Default |
|---|---|---|
| **OKR document** | Path to okr-definition output | Will identify strategic context itself |
| **Vision/strategy document** | Path to vision-crafting output | Will identify strategic context itself |
| **Roadmap format** | Now/Next/Later, time-horizon, or swimlane | Now/Next/Later |
| **Audience** | Primary audience for the roadmap | All three views generated |
| **Time scope** | How far the roadmap looks ahead | 12 months |

## Input schema

```
context:
  type: string
  required: true
  description: Product or project name and context

okr_input:
  type: file_path | string
  required: false
  description: OKR definition output to import

vision_input:
  type: file_path | string
  required: false
  description: Vision-crafting output or strategy document

roadmap_format:
  type: string
  enum: [now-next-later, time-horizon, swimlane]
  default: now-next-later

audience:
  type: string
  enum: [executive, team, customer, all]
  default: all

time_scope:
  type: string
  default: "12 months"

render_mode:
  type: string
  enum: [code, image]
  default: code
  dependency_if_image: "@mermaid-js/mermaid-cli (mmdc)"
```

## Processing rules

### Phase 1 -- Setup

#### Input handling

Follow shared foundation SS7 -- interview mode. When input is missing or insufficient, interview to gather at minimum:

| Dimension | Required | Default |
|---|---|---|
| **Product/project context** | Yes | -- |
| **Roadmap format** | No | Now/Next/Later |
| **Time scope** | No | 12 months |
| **OKR/vision input** | No | Will research context itself |

**Exit interview when**: Context is clear enough to identify themes and initiatives.

#### 1. Collect input

Accept one of:
- A product or project name with context
- A file path to an OKR definition report or vision-crafting report
- Pasted strategic content (OKRs, vision, priorities)
- No input or vague input -> enter interview mode

#### 2. Detect scope

From the input (or interview results), identify:
- **Product/project**: What the roadmap serves
- **Format**: Now/Next/Later, time-horizon, or swimlane
- **Time scope**: How far ahead the roadmap extends
- **Import source**: OKR output, vision output, or none

#### 3. Confirm scope

```
**Product/project**: [name]
**Format**: [now-next-later / time-horizon / swimlane]
**Time scope**: [duration]
**Strategic input**: [imported from OKR/vision / will research]
**Audience views**: [executive, team, customer]
```

Ask the user to confirm or adjust. Ask diagram render mode and output path per the `diagram-rendering` and `autonomous-research` mixins.

### Phase 2 -- Research

Use WebSearch and WebFetch per the `autonomous-research` mixin.

#### 2a. Industry roadmap patterns

Research roadmap patterns for this domain/industry:
- Common themes for similar products or projects
- Typical initiative types and scoping
- Industry-specific considerations (compliance, platform, market)

#### 2b. Best practices

Research roadmapping best practices relevant to the context:
- Theme granularity norms
- Initiative sizing conventions
- Dependency management approaches
- Stakeholder communication patterns

### Phase 3 -- Strategic Context

#### If OKR/vision input is provided

Import strategic context:
- Read the OKR definition output or vision-crafting report
- Extract: objectives, key results, strategic priorities, success metrics
- Map objectives to potential theme areas
- Identify initiative candidates from key results

#### If no strategic input

Identify through research:
- Product/project's stated direction (from website, public sources)
- Market context and competitive landscape
- Likely strategic priorities based on domain
- Current challenges and opportunities

Present strategic context summary for user confirmation.

### Phase 4 -- Theme Identification

Define 3-5 strategic themes.

#### Theme quality criteria

Each theme must be:
- **Strategic**: Connects to an objective or strategic priority
- **Bounded**: Has a clear scope -- what is in and out
- **Measurable**: Has a success metric
- **Justified**: Rationale explains why this theme matters now

#### Theme types

| Type | Description | Example |
|---|---|---|
| **Strategic** | Drives competitive advantage or market position | "Enterprise readiness" |
| **Customer** | Addresses customer needs, pain points, or requests | "Onboarding experience" |
| **Technical** | Addresses platform, infrastructure, or debt | "Scalability & reliability" |

#### Theme table

| # | Theme | Type | Objective link | Success metric | Rationale |
|---|---|---|---|---|---|
| T1 | [theme name] | Strategic | O1: [objective] | [metric] | [why this theme now] |
| T2 | [theme name] | Customer | O2: [objective] | [metric] | [why this theme now] |

Present themes for user confirmation before proceeding to initiatives.

### Phase 5 -- Initiative Mapping

Define 5-15 initiatives mapped to themes.

#### Initiative quality criteria

Each initiative must be:
- **Specific**: Clear scope and expected outcome
- **Sized**: Effort estimate (S/M/L/XL)
- **Linked**: Maps to a theme and optionally to an OKR
- **Outcome-oriented**: Describes what changes, not just what is built

#### Initiative table

| # | Initiative | Theme | Description | Expected outcome | Effort | Dependencies | OKR link |
|---|---|---|---|---|---|---|---|
| I01 | [name] | T1 | [what it involves] | [what changes] | M | -- | KR1.1 |
| I02 | [name] | T1 | [what it involves] | [what changes] | L | I01 | KR1.2 |

### Phase 6 -- Time-Horizon Assignment

#### Now/Next/Later format (default)

| Horizon | Definition | Detail level | Commitment |
|---|---|---|---|
| **Now** | Current quarter / in-progress | High -- specific scope and outcomes | Committed |
| **Next** | Next quarter / planned | Moderate -- known scope, flexible details | Planned |
| **Later** | Beyond next quarter / exploratory | Light -- direction known, scope flexible | Exploratory |

#### Time-horizon format

Map initiatives to specific time periods (Q1/Q2/H1/H2/FY) with the same detail gradient.

#### Swimlane format

Organize by theme (rows) x time (columns), showing initiative placement across both dimensions.

#### Assignment table

| Initiative | Horizon | Rationale | Confidence |
|---|---|---|---|
| I01: [name] | Now | [why now] | High |
| I02: [name] | Next | [why next] | Medium |

### Phase 7 -- Audience Views

Generate three roadmap perspect