prr v0.4.0 — first public release

prr v0.4.0 — first public release

A Claude Code plugin that turns Product Roadmaps Relaunched (C. Todd Lombardo, Bruce McCarthy, Evan Ryan, Michael Connors; O'Reilly, 2017) into a working toolkit for product managers.

The plugin's point of view — taken directly from the book — is that a roadmap is a strategic communication tool, not a project plan. It exists to move PMs from feature-and-date lists to outcome-driven, theme-based roadmaps that communicate strategy and rally stakeholders.

Install

/plugin marketplace add dchuk/prr-plugin
/plugin install prr@prr-marketplace

After install, the product-roadmaps skill is available, eight /prr:* commands are registered, two subagents can be invoked by name, and the validator hook is wired into Write / Edit / MultiEdit.

What's inside

Component	Count	Purpose
Skill	1 (product-roadmaps)	Routing logic that loads the right reference, command, or agent for the task at hand
Slash commands	8	Structured, step-by-step workflows for common roadmap tasks
Subagents	2	Specialized reviewers (roadmap-reviewer, roadmap-relaunch-planner) with narrow scope and their own system prompt
Artifact templates	5	Standard markdown shapes for roadmap, theme, scorecard, change-comm, and special-request files
Validator hook	1	PostToolUse hook (hooks/validate-artifact.py) that enforces frontmatter rules on every Write / Edit / MultiEdit of a managed_by: prr file
Reference files	13	Book-grounded material loaded on demand — 5 core, 3 patterns, 2 anti-patterns, 3 topics

Slash commands

All commands are namespaced /prr:* and accept an optional argument (feature list, file path, vision statement, etc.).

• /prr:build-roadmap-from-vision — Construct a full roadmap skeleton from company vision down to themes, business objectives, Now/Next/Later timeframes, and a disclaimer.
• /prr:import-roadmap — Convert an existing roadmap in any format (PDF, CSV, JSON, markdown) into the prr template format, with an import report showing transformations and anti-patterns found.
• /prr:transform-features-to-themes — Convert a list of feature requests or deliverables into outcome-oriented themes by uncovering the underlying customer need.
• /prr:build-roi-scorecard — Build a defensible ROI Scorecard ranking themes or features using Value / Effort × Confidence so prioritization isn't driven by gut or politics.
• /prr:run-shuttle-diplomacy — Plan and run one-on-one stakeholder meetings followed by a group alignment session to build buy-in before finalizing a roadmap.
• /prr:evaluate-special-request — Evaluate an ad-hoc sales or stakeholder request using the book's three qualifying questions and iron-triangle trade-off analysis.
• /prr:assess-roadmap-health — Run the 14-question Roadmap Health Assessment (0–2 per question, max 22 points) and recommend course corrections (Approach A) or full relaunch (Approach B).
• /prr:communicate-roadmap-change — Draft an audience-aware stakeholder communication for any roadmap change — from a minor date slip to a strategic pivot.

Subagents

• roadmap-reviewer — Audits a roadmap artifact against the book's principles, rules, and anti-patterns. Checks for the five primary components, feature-date thinking, output-vs-outcome framing, missing strategic context, overpromising, Feature Factory patterns, bad prioritization, consensus-seeking, Osborne Effect risks, orphaned themes, iron triangle violations, and commitment-style language. Operates in structured mode when files carry managed_by: prr frontmatter — it parses YAML directly for mechanical checks and falls back to prose review otherwise. Output is severity-ranked (Critical / High / Medium / Low) with rule citations and concrete corrections.
• roadmap-relaunch-planner — Plans a roadmap relaunch or improvement initiative. Runs the Roadmap Health Assessment, chooses between Approach A and Approach B, sequences the six-step relaunch process, identifies the highest-leverage improvements, structures roadmap workshops, and builds a steering-committee cadence.

Artifact templates

Every artifact the plugin produces has a standard markdown shape with YAML frontmatter, so commands can read/write each other's output and the roadmap-reviewer agent can audit it mechanically.

• roadmap.md — vision, OKRs, disclaimer, Now/Next/Later tables
• theme.md — one file per theme with customer need, linked objectives, evidence, optional ROI score
• roi-scorecard.md — (Value / Effort) × Confidence prioritization
• change-communication.md — audience-aware change announcement
• special-request.md — three-qualifying-questions evaluation

Default on-disk layout:

<your project>/
├── roadmap.md
├── themes/
│   ├── ensure-seamless-checkout.md
│   └── ensure-faster-onboarding.md
└── artifacts/
    ├── scorecard-2026-04-13.md
    ├── change-2026-04-20-defer-reporting.md
    └── request-2026-04-22-acme-sso.md

Structural constraints (enforced by the validator hook)

Frontmatter enforces book-grounded rules so anti-patterns can't slip through unnoticed:

• timeframe is restricted to Now | Next | Later — no calendar dates.
• confidence is an integer 0–99 — never 100%, the book's "fake-precision" anti-pattern.
• linked_objectives is required and non-empty — no orphaned themes.
• disclaimer is required on every roadmap.
• prioritization_method must be declared explicitly (roi-scorecard | dfv | kano | moscow | critical-path).
• Every file carries a type: discriminator (roadmap | theme | roi-scorecard | change-communication | special-request-evaluation) so agents can filter artifacts with a single grep.

The hooks/validate-artifact.py PostToolUse hook runs after every Write / Edit / MultiEdit:

• Only inspects files that declare managed_by: prr in their YAML frontmatter — existing roadmap.md or themes/*.md files without that marker are never touched.
• Validates type-specific rules (required fields, enum values, integer ranges) against the book's prescriptions.
• On failure, exits with code 2 and prints actionable errors to stderr; Claude sees the message and self-corrects in the same conversation.
• Zero third-party dependencies — pure Python stdlib, uses python3 (preinstalled on macOS and most Linux distros).

To opt out on a single file, omit managed_by: prr from its frontmatter. To disable globally, remove the hook from ~/.claude/settings.json after install.

Reference tree

The product-roadmaps skill loads reference files on demand from skills/product-roadmaps/references/:

references/
├── core/
│   ├── roadmap-definition.md
│   ├── roadmap-components.md
│   ├── vision-strategy-okrs.md
│   ├── themes-and-needs.md
│   └── gathering-inputs.md
├── patterns/
│   ├── prioritization-frameworks.md
│   ├── alignment-and-buyin.md
│   └── presenting-and-sharing.md
├── anti-patterns/
│   ├── roadmap-anti-patterns.md
│   └── bad-prioritization.md
└── topics/
    ├── relaunch-process.md
    ├── keeping-roadmap-fresh.md
    └── glossary.md

Two on-ramps

Path A — Start a new roadmap from scratch. Open a working directory, run /prr:build-roadmap-from-vision, walk through the book's eight-step process, and the plugin writes roadmap.md and themes/<slug>.md for you.

Path B — Import an existing roadmap. Export your current roadmap to a file Claude can read (CSV / JSON from Jira Product Discovery, Aha!, Productboard, Roadmunk; PDF from slide decks; markdown from Notion or Confluence; CSV from spreadsheets), then run /prr:import-roadmap ./imports/<file>. The plugin classifies what you have, extracts the five primary components, asks about gaps, and writes the converted files plus an import report (artifacts/import-YYYY-MM-DD.md) explaining every transformation and every anti-pattern detected.

In both cases, follow up with the roadmap-reviewer subagent for a structured audit before sharing.

Who this is for

• PMs starting a new roadmap with no skeleton yet.
• PMs who inherited a roadmap that's drifted into a feature-and-dates list.
• Founders, heads of product, and team leads who need a defensible, outcome-driven roadmap for a board, investors, or exec staff.
• PMs trapped in tools (Jira Product Discovery, Aha!, Productboard, Notion, slide decks) who want a markdown-native, git-trackable source of truth.
• PMs under stakeholder pressure — sales escalations, exec pet features, customer commitment requests — who need a rigorous framework to say yes, defer, or no.
• Anyone tasked with reviewing a roadmap (auditor, peer reviewer, hiring panelist, new VP of Product) who wants a structured rubric instead of vibes.

Philosophy

This plugin doesn't invent guidance. Every pattern, rule, score, and anti-pattern traces back to Product Roadmaps Relaunched (Lombardo, McCarthy, Ryan, Connors; O'Reilly, 2017). When the book is silent, the agents and commands are instructed to say so rather than extrapolate.

Compatibility

• Claude Code plugin format with marketplace.json and plugin.json manifests.
• PostToolUse validator hook uses pure Python 3 stdlib — no third-party dependencies.
• Tested with Claude Code's Write / Edit / MultiEdit tool flow.

Credits

Generated by Franklin from Product Roadmaps Relaunched, then hand-refined for skill/command/hook best practices.

License

MIT