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.
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-codeWrote 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/commands/lucasgaravelli/pm-skills-claude-code/roadmap)<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/roadmap"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/roadmap.svg" alt="Measured on agentmods" 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.00000 | $0.04111 |
| Opus 5 | $0.00000 | $0.02056 |
| Sonnet 5 | $0.00000 | $0.00822 |
| Haiku 4.5 | $0.00000 | $0.00411 |
Grade A, and why
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 7d 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.
This is a copy
100% identical to roadmap — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/roadmap
O que essa skill faz
Cria roadmap trimestral (ou semestral) com fases de features, sequenciamento, dependências e trade-offs.
Saída: Roadmap visual com timeline clara, team alocação, e critério de sucesso por fase.
Quando usar
- Fim de trimestre, precisa comunicar Q próximo para todo time
- Muitas features, precisa sequenciar e mostrar dependências
- Board quer ver plano de 3-6 meses
Input esperado
Mínimo:
- Features priorizadas: Lista de 5-10 features em ordem de prioridade (use /prioritize se não tem)
- Team size: Quantos eng, design, PM
- Constraints: Holidays, launches, experiments
Opcional:
- Timeline detalhada de features (da /user-stories)
- Dependências técnicas
- Marketing calendar
- Eventos de negócio (conference, product release)
Processo
- Phases — Agrupar features em 3-4 fases
- Timeline — Quando cada phase sai (semanas)
- Team allocation — Quem faz cada phase
- Dependencies — Qual phase bloqueia qual
- Milestones — Go-live dates, launch events
- Buffer — Tempo para surpresas
Output
# Roadmap: [Produto] — [Trimestre/Período]
## Visão geral
**Meta desse período:** [O que vamos conseguir]
**Team:** [X eng, Y design, Z PM]
**Timeline:** [Data start - data end]
---
## Timeline Visual
Jan Feb Mar Apr
─────────────────────────
P1 🔨 ━━━━━ (Deal war rooms) P2 🔨 ━━━━━━━━━ (Email sync) P3 🔨 ━━━━━━ (Deal health) P4 🔨 ━━━ (Mkt) (Enterprise features) ───────────────────────── Budget: [X eng weeks]
---
## Phase 1: [Nome] — [Semana start/end]
### O que entra
- Feature A
- Feature B (parte 1)
### Por quê essa phase?
[Razão estratégica — qual meta de negócio resolve]
### Timeline
- Week 1-2: Build core
- Week 3: QA + polish
- Week 4: Rollout + monitoring
### Go-live: [Data]
### Team
- Eng: [X eng dedicadas]
- Design: [Y horas]
- PM: [Z horas]
### Success criteria
- Feature adoption: [X%]
- Métrica move: [Y%]
- No performance regression: < 3% latency increase
### Risks
- [Risk 1]: Mitigação
- [Risk 2]: Mitigação
### Dependencies
- Precisa de [Fase anterior] ou [Ferramenta]
- Desbloqueia [Fase seguinte]
---
## Phase 2: [Nome] — [Semana start/end]
[Mesmo formato]
---
## Phase 3: [Nome] — [Semana start/end]
[Mesmo formato]
---
## Phase 4: [Nome] (Se houver)
[Mesmo formato]
---
## Sequência e Dependências
Phase 1 ──────────┐ ├──> Phase 2 │ Phase 1b ─────────┘
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.
- 7d ago First seen · 564 lines · 0 tokens per session scan A 2eb9152bb0b5
roadmap is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,111 tokens. A static security scan graded it A with 0 findings. It is 100% identical to roadmap, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.