What is productplan-customer-facing?

Instructions for creating customer-facing roadmap views and launch timelines from ProductPlan, a tool for planning and presenting product releases.

Use it to answer questions about upcoming, recently released, or planned features and to prepare timelines for sales or customer-success calls.

Roadmap data can be too detailed or technical for customer conversations. These instructions explain how to find launches, release dates, roadmap lanes, and high-level themes to share clearly.

productplan-customer-facing — Skill for Claude Code and Codex by olgas

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add olgasafonova/productplan-mcp-server --skill productplan-customer-facing

Clone the repo

git clone --depth 1 https://github.com/olgasafonova/productplan-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing/github.svg)](https://agentmods.dev/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing)

Your own site

<a href="https://agentmods.dev/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing"><img src="https://agentmods.dev/badge/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing"><img src="https://agentmods.dev/badge/skills/olgasafonova/productplan-mcp-server/productplan-customer-facing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,288 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.01288
Opus 5	$0.00023	$0.00644
Sonnet 5	$0.00009	$0.00258
Haiku 4.5	$0.00005	$0.00129

Measured 10d ago against content hash 5fa6335bb117, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

productplan-customer-facing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/productplan-customer-facing/SKILL.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ProductPlan for Sales & Customer Success

Customer-ready roadmap views and release timelines.

Quick Answers for Customer Calls

"What's coming soon?"

Call list_launches to see upcoming releases
Filter for launches in the next 30-90 days
Present as a timeline customers can understand

"When will feature X be available?"

Call get_roadmap_complete for the relevant product
Search bars for the feature name
Report the end_date as the expected availability

"What did you recently release?"

Call list_launches
Filter for completed launches
Summarize recent releases with key highlights

"What's on the roadmap for this year?"

Call get_roadmap_complete for the product
Summarize features by quarter
Present high-level themes, not granular details

Roadmap Views

Get product roadmap overview

Call list_roadmaps to find the right product
Call get_roadmap_complete with roadmap_id
Format as customer-friendly timeline

View by lane/category

Lanes represent categories (e.g., "Platform", "Integrations", "UX"):

Call get_roadmap_lanes to see categories
Call get_roadmap_bars to get features
Group features by lane for themed presentations

Key milestones

Call get_roadmap_milestones to get major dates:

Beta releases
GA launches
Conference announcements

Launch Information

Upcoming launches

Call list_launches for all scheduled releases.

Key fields for customers:

Launch name
Target date
Status (on track, delayed)

Launch details

Call get_launch with launch_id for:

Full description
Included features
Release notes draft

Customer Feedback Loop

Check if idea exists

Call list_ideas
Search for the customer's request
If found, share current status and vote count

Log customer request

Call manage_idea with action="create", title, description to capture:

Feature requests from calls
Enhancement suggestions
Pain points mentioned

Read the full file on GitHub · 194 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 194 lines · 47 tokens per session scan A 5fa6335bb117

Subscribe to this mod's changes

productplan-customer-facing is a skill published in the GitHub repository olgasafonova/productplan-mcp-server (3 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 1,288 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Go Project management anthropic claude go mcp mcp-server

miro-workflow

Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…

olgasafonova/miro-mcp-server · 103 tokens

miro-boards

Create and manage Miro board content including stickies, shapes, connectors, diagrams, and mindmaps. Use for whiteboard collaboration, sprint planning, retrospectives, and brainstorming.

olgasafonova/miro-mcp-server · 41 tokens

go-expert

Expert-level Go development with Go 1.22+ features, concurrency, standard library, and production-grade best practices. Use when the user mentions concurrency, microservices, or backend, or when the task involves idiomatic Go, goroutines and channels, context-based cancellation, or writing an HTTP server.

personamanagmentlayer/pcl · 65 tokens

productplan-customer-facing