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 liqiongyu/lenny_skills_plus --skill prioritizing-roadmapgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/prioritizing-roadmap)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/prioritizing-roadmap"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/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/liqiongyu/lenny_skills_plus/prioritizing-roadmap"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/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.00030 | $0.01887 |
| Opus 5 | $0.00015 | $0.00944 |
| Sonnet 5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00189 |
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 12d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritizing Roadmap
Scope
Covers
- Turning messy roadmap inputs into a ranked opportunity list + coherent roadmap
- Defining a planning “season” (macro context) and success criteria
- Using a common-currency scoring model (ICE + assumptions) to compare across teams
- Producing an alignment-ready Roadmap Prioritization Pack
When to use
- “What should we build next?”
- “We need a Q2/Q3 roadmap.”
- “We have too many requests and no way to compare them.”
- “We need to prioritize across multiple teams/pods.”
When NOT to use
- You don’t have any agreed goal / North Star / strategic intent (do product vision / goals first; use
setting-okrs-goals). - You need sprint planning or story-level estimation (use your agile/scrum process).
- You’re only choosing a single experiment within an already-fixed roadmap.
- You need a full customer discovery plan from scratch (use
problem-definition). - You need to cut scope within an already-committed project (use
scoping-cutting). - You need an engineering/technical roadmap for infrastructure or platform work (use
technical-roadmaps). - You need to track milestones, deadlines, and delivery status on an existing plan (use
managing-timelines).
Inputs
Minimum required
- Product + primary customer segment
- Planning horizon + cadence (e.g., next 6 weeks, next quarter, rolling 12–24 months)
- Success criteria (North Star / business goal) + 2–5 guardrails
- Candidate opportunities (or current roadmap/backlog) with rough size/effort
- Constraints: capacity, commitments, dependencies, deadlines, risk tolerance
Missing-info strategy
- Ask up to 5 questions from references/INTAKE.md.
- If still missing, proceed with clearly labeled assumptions and provide 2–3 roadmap options.
Outputs (deliverables)
Produce a Roadmap Prioritization Pack in Markdown (in-chat; or as files if requested):
- Context snapshot (goal, horizon, constraints, stakeholders)
- Season framing (what changed, key bets, explicit non-goals)
- Opportunity inventory with conviction level (known vs hypothesis) and evidence
- Prioritization model (common currency + ICE scoring + assumptions)
- Ranked opportunity list (top 10–20) + “parking lot”
- Roadmap draft (Now/Next/Later or quarterly themes) + update cadence (rolling plan)
- Decision narrative (why these, why now) + “Think Bigger” ideas
- Risks / Open questions / Next steps (always included)
What ships with it
13 files 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.
- eval/eval_config.json 1.3 KB
- eval/SHOWCASE.md 5.9 KB
- eval/with_skill.md 33 KB
- eval/without_skill.md 11 KB
- README.md 1.8 KB
- references/CHECKLISTS.md 2.3 KB
- references/EXAMPLES.md 6.3 KB
- references/INTAKE.md 2.1 KB
- references/RUBRIC.md 3.7 KB
- references/SOURCE_SUMMARY.md 1.8 KB
- references/TEMPLATES.md 3.5 KB
- references/WORKFLOW.md 4.2 KB
- skillpack.json 384 B
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.
- 12d ago First seen · 135 lines · 30 tokens per session scan A e4c993e57835
prioritizing-roadmap is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,887 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
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.