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.
npx skills add cnfeat/top-pm-skills --skill prioritizing-roadmapgit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote 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.
[](https://agentmods.dev/skills/cnfeat/top-pm-skills/prioritizing-roadmap)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/prioritizing-roadmap"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/prioritizing-roadmap/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.
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/prioritizing-roadmap"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/prioritizing-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00046 | $0.01018 |
| Opus 5 | $0.00023 | $0.00509 |
| Sonnet 5 | $0.00009 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
prioritizing-roadmap 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritizing Roadmap
Help the user prioritize product roadmaps and backlogs using frameworks from 75 product leaders.
How to Help
When the user asks for help with prioritization:
- Understand the decision context - Ask about their goals, constraints, and stakeholder landscape
- Assess the portfolio - Determine if they need to balance incremental vs big bets, or core vs new
- Provide frameworks - Recommend appropriate prioritization approaches for their situation
- Challenge assumptions - Help them question whether their current priorities are truly the most impactful
Core Principles
Separate truth from hypothesis
Alex Hardimen: "The idea of being able to take all of these crazy inputs, trying to create a very structured model to figure out, 'Okay, what is true? Where do we have conviction? Where do we have questions?'" Categorize inputs by conviction level vs. questions and rally the team around a shared context.
Use "seasons" in fast-changing markets
Asha Sharma: "We think about it as what season are we in? Season one might've been prototyping of AI and then it was all around models and reasoning models, and now it's the advent of agents." In rapidly changing environments, align the team on secular market shifts rather than rigid long-term roadmaps.
Build a common currency for comparison
Dan Hockenmaier: "The most difficult thing about making that kind of effort is developing a common currency by which you can trade off their efforts... The growth model is the function that lets you do that." Use growth models to make projected impacts comparable across different teams during planning.
Force big thinking in planning
Eeke de Milliano: "At the bottom of every team charter we have a section called, Think Bigger. 'With 20% more time, what would you do that isn't on this list already?'" Explicitly ask for big ideas in planning documents to prevent teams from only focusing on incremental improvements.
Balance cannonballs and lead bullets
Adriel Frederick: "I'm going to have some cannonballs... and I'm going to have a bunch of lead bullets. Maybe it's 80% of your energies on those big cannonballs, 20% on the lead bullets." A healthy roadmap balances high-investment "cannonballs" with incremental "lead bullets" to avoid purely incremental thinking.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 72 lines · 46 tokens per session scan A f8d28a49f38a
prioritizing-roadmap is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,018 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.