Product-org-os roadmap-item

'Define a specific roadmap item with scope, dependencies, and success criteria. Activate when: "add to the roadmap", "roadmap item", "plan this initiative", single initiative detail, roadmap

install

source · Clone the upstream repo

git clone https://github.com/yohayetsion/product-org-os

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/yohayetsion/product-org-os "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/roadmap-item" ~/.claude/skills/yohayetsion-product-org-os-roadmap-item && rm -rf "$T"

manifest: skills/roadmap-item/SKILL.md

source content

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/item.md` )	UPDATE	100%
Item ID mentioned ( `RI-2026-001` )	UPDATE	100%
"create", "new", "draft" in input	CREATE	100%
"find", "search", "list items"	FIND	100%
"the item", "the initiative"	UPDATE	85%
Just item name	CREATE	60%

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

Mode Behaviors

CREATE: Generate complete new roadmap item using template below.

UPDATE:

Read existing item (search if path not provided)
Preserve unchanged sections exactly
Update status, priority, timeline, or scope
Show diff summary: "Updated: [sections]. Unchanged: [sections]."

FIND:

Search paths below for roadmap items
Present results: item name, ID, status, theme
Ask: "Update one of these, or create new?"

Search Locations for Roadmap Items

```
roadmap/items/
```
```
roadmap/
```
```
backlog/
```
```
epics/
```

Define a Roadmap Item (initiative, epic, or feature).

Vision to Value Phase

Phase 3: Strategic Commitments - Roadmap items are the specific commitments within themes.

Prerequisites: Roadmap theme defined, capacity understood Outputs used by: PRDs, feature specs, sprint planning

Output Structure

# Roadmap Item: [Item Name]

**Item ID**: RI-[YYYY]-[NNN]
**Type**: Epic / Feature / Initiative
**Theme**: [Parent theme]
**Owner**: [Name]
**Status**: Proposed / Planned / In Progress / Completed

## Overview

**Description**: [What this item delivers]

**Customer Problem**: [What customer problem it solves]

**Value Proposition**: [Why customers care]

## Priority

**Priority**: P0 (Must have) / P1 (Should have) / P2 (Nice to have)

**Prioritization Rationale**:
- Strategic alignment: [High/Med/Low]
- Customer demand: [High/Med/Low]
- Revenue impact: [High/Med/Low]
- Effort: [S/M/L/XL]

## Target Timeline

**Target Quarter**: [Quarter]
**Target Release**: [Release/Version]
**Confidence**: High / Medium / Low

## Success Criteria

| Metric | Target | Timeframe |
|--------|--------|-----------|
| [Metric 1] | [Target] | [When] |
| [Metric 2] | [Target] | [When] |

## Scope

**In Scope**:
- [Item 1]
- [Item 2]
- [Item 3]

**Out of Scope**:
- [Item 1]
- [Item 2]

**Future Considerations**:
- [Item 1]

## Dependencies

| Dependency | Type | Owner | Status | Blocking? |
|------------|------|-------|--------|-----------|
| [Dependency] | Technical/Resource/External | [Owner] | [Status] | Yes/No |

## Risks

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

## Effort Estimate

**T-Shirt Size**: S / M / L / XL
**Engineering**: [Estimate]
**Design**: [Estimate]
**Other**: [Estimate]

## Related Items

- [Link to related roadmap items]
- [Link to PRD if exists]

Instructions

Ask about the parent theme if not clear
Reference any related documents via @file syntax
Include clear success criteria
Be explicit about scope boundaries
Save in roadmap/ folder