agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/roadmap-update/SKILL.md

roadmap-update

Skill1 starsChanged 7 months agoMITView on GitHub

Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later framework. Trigger phrases: "update the roadmap", "roadmap planning", "reprioritize roadmap", "what should we build next", "adjust the timeline", "roadmap review", "now next later", "shift priorities", "add to roadmap", "quarterly planning"

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update, create, or reprioritize product roadmaps.

    line 12
  2. Distinctive:

    Before making changes, establish:

    line 18
  3. Distinctive:

    When adding or reprioritizing, make trade-offs explicit:

    line 57
  4. Distinctive:

    Response: Start with strategic goals for the quarter.

    line 124
  5. Distinctive:

    Roadmaps are living documents: Update them when reality changes, not on a fixed schedule.

    line 128
  6. Distinctive:

    Make trade-offs visible: When something is added, something else must move.

    line 131
  7. Distinctive:

    Limit Now items: If everything is Now, nothing is prioritized.

    line 132
  8. Distinctive:

    Communicate changes proactively: When the roadmap shifts, tell affected stakeholders before they ask.

    line 134

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Roadmap Update

Update, create, or reprioritize product roadmaps. Handle additions, timeline shifts, priority changes, and framework structuring using Now/Next/Later or time-based approaches.

Workflow

Step 1: Understand the Current State

Before making changes, establish:

  1. Existing roadmap: What is already planned? Ask for the current roadmap or work from context.
  2. Framework in use: Time-based (Q1/Q2/Q3), Now/Next/Later, or custom?
  3. Change trigger: What prompted this update? New information, dependency change, strategic shift, customer escalation?
  4. Constraints: Team size, key dependencies, deadlines, commitments already communicated externally.

Step 2: Classify the Update

Update TypeApproach
Add initiativeAssess priority, find where it fits, identify what it displaces
Remove/deprioritizeDocument rationale, identify downstream impacts, communicate
Timeline shiftCascade dependencies, assess impact on commitments
Full reprioritizationRe-evaluate all items against current strategy and constraints
New roadmapStart from strategy and goals, populate with initiatives

Step 3: Apply the Now/Next/Later Framework

Now (Current quarter, committed):

  • Team is actively working on these
  • Scope is defined, requirements are clear
  • Stakeholders have been informed
  • Contains only what fits in current capacity

Next (1-2 quarters out, high confidence):

  • Problem is validated, solution direction is known
  • Dependencies are identified
  • Will move to Now when current items ship
  • Can be described at the epic level

Later (3+ quarters, exploratory):

  • Strategic bets and opportunities
  • Problem is understood but solution is not locked
  • Subject to change based on learnings from Now/Next
  • Captured at the theme level

Step 4: Prioritize with Trade-offs

When adding or reprioritizing, make trade-offs explicit:

### Proposed Change: [Add/Move/Remove] [Initiative]

**Rationale**: [Why this change is needed]
**Impact if we do it**: [What we gain]
**Impact if we don't**: [What we risk]
**What it displaces**: [What moves down or out to make room]
**Dependencies**: [What needs to be true for this to work]
**Stakeholders to inform**: [Who needs to know about this change]

Prioritization criteria:

  • Strategic alignment: Does this move a company or team OKR?
  • Customer impact: How many users benefit? How much does it matter to them?
  • Revenue impact: Does this unlock revenue, prevent churn, or enable expansion?
  • Effort: T-shirt size estimate (S/M/L/XL) and team required
  • Risk of delay: What happens if we wait another quarter?

Step 5: Produce the Updated Roadmap

## Product Roadmap: [Team/Product]
Last updated: [Date]

### Strategic Context
[1-2 sentences on current strategy and goals]

### Now (Q[X] [Year])
| Initiative | Goal | Status | Owner | Size |
|-----------|------|--------|-------|------|
| [Name] | [Outcome] | In Progress / Scoping | [Name] | M |

### Next (Q[X+1])
| Initiative | Goal | Confidence | Dependencies |
|-----------|------|------------|-------------|
| [Name] | [Outcome] | High/Med | [Deps] |

### Later (H[X])
| Theme | Opportunity | Open Questions |
|-------|------------|----------------|
| [Theme] | [Description] | [What we need to learn] |

### Recently Completed
| Initiative | Shipped | Outcome |
|-----------|---------|---------|
| [Name] | [Date] | [Result/metric] |

### Changelog
| Date | Change | Rationale |
|------|--------|-----------|
| [Date] | [What changed] | [Why] |

Examples

Example 1: Adding a New Initiative

User: "We need to add SSO support. Where does it fit?" Response: Assess SSO against current priorities. Ask who is requesting it (enterprise customers, security audit, sales blocker). Determine size. Identify what it displaces. If it is a sales blocker, it may jump to Now; if it is a nice-to-have, it goes to Next or Later.

Example 2: Timeline Slip

User: "The payments integration is going to take 3 more weeks." Response: Cascade the delay. What was supposed to start after payments? Can anything be pulled forward? Update the roadmap with new dates and flag any external commitments at risk.

Example 3: Quarterly Planning

User: "Help me plan next quarter's roadmap." Response: Start with strategic goals for the quarter. Pull from the current Next bucket. Assess team capacity (subtract PTO, on-call, maintenance). Propose 2-3 major initiatives and 1-2 smaller items. Leave 20% buffer for unplanned work.

Best Practices

  1. Roadmaps are living documents. Update them when reality changes, not on a fixed schedule. A stale roadmap is worse than no roadmap.
  2. Outcomes over outputs. Frame initiatives by what they achieve ("reduce churn by 2pp") not what they build ("add feature X").
  3. Protect capacity for maintenance. Reserve 15-20% of engineering time for bugs, tech debt, and operational work. Do not roadmap 100% of capacity.
  4. Make trade-offs visible. When something is added, something else must move. Never say "we'll just fit it in." Show what gives.
  5. Limit Now items. If everything is Now, nothing is prioritized. Two to four major initiatives per team per quarter is typical.
  6. Keep Later loose. Later items will change. Do not over-specify them. Themes and problem statements are sufficient.
  7. Communicate changes proactively. When the roadmap shifts, tell affected stakeholders before they ask. Include the rationale.
  8. Track accuracy over time. Compare planned vs. actual quarterly. If accuracy is below 60%, you are overcommitting or underprioritizing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.