Product Roadmap Theme Definition

VerifiedSafe

Defines a single roadmap theme with grouped initiatives and success metrics. Helps organize roadmap commitments around strategic priorities. Supports creating new themes, updating existing ones, or finding themes across the project.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#roadmap-theme#product-planning#initiative-grouping#strategy

Recommended for

Automated summary

This skill defines a single roadmap theme with grouped initiatives and success metrics, supporting create, update, and find modes.

Strengths

  • Complete and standardized template for a roadmap theme
  • Automatic mode detection (create, update, find)
  • Integration with existing roadmap structure via IDs and file paths
  • Shows diff summary on updates

Limitations

  • Requires strategic bets and roadmap structure prerequisites
  • Only handles one theme at a time, not a full roadmap
  • Fixed output format with limited customization
When to use it

Use this skill to organize a roadmap theme with initiatives, metrics, and risks, typically during quarterly planning.

When not to use it

Do not use for a full multi-theme roadmap or for detailing a single initiative.

Security analysis

Safe
Quality score88/100

The skill only generates a markdown document template for a roadmap theme, with no declared or implied execution of system commands, network operations, or destructive actions. File operations are limited to reading within specified safe paths.

No concerns found

How this analysis is made

Examples

Create a new theme
Define a roadmap theme for Q3 focused on customer acquisition.
Group initiatives under a theme
Group these initiatives under a theme: launch referral program, improve onboarding, optimize ad spend.
Update existing theme
Update the roadmap theme RT-2025-001 with a new initiative for AI chatbot.

name: roadmap-theme description: | Define a single roadmap theme with grouped initiatives and success metrics. Activate when: "define a roadmap theme", "group these initiatives", "theme for Q3", thematic roadmap organization, initiative grouping Do NOT activate for: full roadmap with multiple themes (/product-roadmap), detailing a single initiative (/roadmap-item), strategic intent (/strategic-intent) argument-hint: [theme name] or [update path/to/theme.md] user-invocable: true metadata: author: Product Org OS version: 3.0.0 category: roadmap compatibility: Requires Product Org OS v3+ context layer and rules

Document Intelligence

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

Mode Detection

| Signal | Mode | Confidence | |--------|------|------------| | "update", "revise", "modify" in input | UPDATE | 100% | | File path provided (@path/to/theme.md) | UPDATE | 100% | | Theme ID mentioned (RT-2026-001) | UPDATE | 100% | | "create", "new", "draft" in input | CREATE | 100% | | "find", "search", "list themes" | FIND | 100% | | "the theme", "the Growth theme" | UPDATE | 85% | | Just theme name | CREATE | 60% |

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

Mode Behaviors

CREATE: Generate complete new roadmap theme using template below.

UPDATE:

  1. Read existing theme (search if path not provided)
  2. Preserve unchanged sections exactly
  3. Add/modify initiatives, update metrics
  4. Show diff summary: "Updated: [sections]. Unchanged: [sections]."

FIND:

  1. Search paths below for roadmap themes
  2. Present results: theme name, ID, owner, path
  3. Ask: "Update one of these, or create new?"

Search Locations for Roadmap Themes

  • roadmap/themes/
  • roadmap/
  • strategy/themes/
  • planning/

Define a Roadmap Theme with initiatives and success criteria.

V2V Phase

Phase 3: Strategic Commitments - Themes organize roadmap commitments around strategic priorities.

Prerequisites: Strategic bets defined, roadmap structure established Outputs used by: Roadmap items, resource allocation, quarterly planning

Output Structure

# Roadmap Theme: [Theme Name]

**Theme ID**: RT-[YYYY]-[NNN]
**Owner**: [Role/Name]
**Timeframe**: [Quarters covered]
**Investment**: [% of capacity]

## Theme Overview

**Description**: [What this theme is about - 1-2 sentences]

**Strategic Rationale**: [Why this theme matters to the business]

**Customer Value**: [What value customers get from this theme]

## Strategic Alignment

**Supports Strategic Bet**: [Link to strategic bet]
**Company Goal**: [Which company goal this serves]

## Success Metrics

| Metric | Baseline | Target | Timeframe |
|--------|----------|--------|-----------|
| [Metric 1] | [Current] | [Target] | [When] |
| [Metric 2] | [Current] | [Target] | [When] |
| [Metric 3] | [Current] | [Target] | [When] |

## Initiatives

### Initiative 1: [Name]
**Description**: [Brief description]
**Priority**: P0 / P1 / P2
**Effort**: S / M / L / XL
**Owner**: [Name]
**Target Quarter**: [Quarter]
**Dependencies**: [Dependencies]
**Success Criteria**: [How we know it's done well]

### Initiative 2: [Name]
[Same structure]

### Initiative 3: [Name]
[Same structure]

## Quarterly Breakdown

| Quarter | Initiatives | Capacity | Key Deliverables |
|---------|-------------|----------|------------------|
| [Q1] | [Initiatives] | X% | [Deliverables] |
| [Q2] | [Initiatives] | X% | [Deliverables] |

## Dependencies

| Dependency | Type | Owner | Status | Risk |
|------------|------|-------|--------|------|
| [Dependency] | Internal/External | [Owner] | [Status] | High/Med/Low |

## Risks

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk] | High/Med/Low | High/Med/Low | [Plan] |

## Resource Requirements

- **Team**: [Who's needed]
- **Skills**: [What skills required]
- **External**: [External resources needed]

Instructions

  1. Ask about strategic alignment if not clear
  2. Reference any roadmap or strategy documents via @file syntax
  3. Include clear success metrics per theme
  4. Break down into concrete initiatives
  5. Save in roadmap/ folder

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/product-roadmap-theme-definition-mm78noa1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/product-roadmap-theme-definition-mm78noa1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/product-roadmap-theme-definition-mm78noa1/download' --output '.skill-downloads/product-roadmap-theme-definition-mm78noa1/SKILL.md.part' && mv '.skill-downloads/product-roadmap-theme-definition-mm78noa1/SKILL.md.part' '.skill-downloads/product-roadmap-theme-definition-mm78noa1/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/product-roadmap-theme-definition-mm78noa1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills