strategy

strategy is a command for Claude Code from lucasgaravelli/pm-skills-claude-code. It costs 0 tokens per session (3,333 once invoked), scanned A, a copy of strategy, MIT.

A product-strategy canvas covering the vision, target users, problem, solution, differentiation, business model, metrics, roadmap, and risks. It is a short document for aligning the people responsible for a product.

In plain words
What is it for?
Use it to describe where a product should go, who it serves, how it will make money, how progress will be measured, and what should happen over the next three quarters.
Why use it?
It brings scattered product decisions into one coherent plan and makes the reasons, measures of success, and possible problems easier to discuss.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

Good fit Use it to describe where a product should go, who it serves, how it will make money, how progress will be measured, and what should happen over the next three quarters.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lucasgaravelli/pm-skills-claude-code/strategy
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.

Clone the repo
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-code

Made for: Claude Code.

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.

agentmods badge for strategy

README.md
[![agentmods](https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/strategy.svg)](https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/strategy)
Your own site
<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/strategy"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,333 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03333
Opus 5 $0.00000 $0.01666
Sonnet 5 $0.00000 $0.00667
Haiku 4.5 $0.00000 $0.00333

Measured 8d ago against content hash 6309a5fc11e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

strategy 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 8d 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.

Origin

This is a copy

100% identical to strategy — 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.

.claude/commands/strategy.md · 426 lines

How it starts

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

/strategy

O que essa skill faz

Desenha estratégia de produto em 9 seções (canvas): Visão, Segmento, Problema, Solução, Diferenciação, Monetização, Métricas, Roadmap, Riscos.

Saída: Canvas de estratégia em 1-2 páginas, pronto para alinhamento com stakeholders.


Quando usar

  • Trimestre novo, precisa de alinhamento estratégico
  • Mudança de direção — precisa comunicar o "why"
  • Apresentar para board ou investors — precisa de narrativa coerente

Input esperado

Mínimo:

  • Visão: Onde você quer que o produto seja em 3-5 anos
  • Problema: Qual market pain está atacando
  • Segmento: Quem são seus usuários principais

Opcional:

  • Dados de mercado (TAM, competição)
  • Roadmap de 2-3 trimestres
  • Constraints (budget, team)

Processo

  1. Visão — Inspiradora mas realizável
  2. Segmento — Específico, não "everyone"
  3. Problema-Solução — Claro e validado
  4. Diferenciação — Por que você vs outros?
  5. Monetização — Como ganha dinheiro?
  6. Métricas — Como sabe que está ganhando?
  7. Roadmap — Próximos 3 trimestres
  8. Riscos — O que pode dar errado?
  9. Call to action — Próximo passo

Output

# Estratégia de Produto: [Produto/Divisão]

## 1. Visão (3-5 anos)

**1 frase que inspira:**
[Descrição clara de futuro desejado — não "ser líder", seja específico]

**Expansão:**
[2-3 parágrafos sobre que mundo estamos criando]

---

## 2. Segmento Alvo

### Primário
- **Descrição**: [Tipo de empresa, rol, tamanho]
- **Tamanho de mercado**: [# de empresas × # de users/empresa]
- **TAM**: [$X market size]
- **Porquê esse segmento**: [Razão — problema é urgent, $ disponível, etc]

### Secundário
- **Descrição**: [Outro segmento possível no futuro]
- **Quando**: [Trimestre que vamos atacar]

### Deliberadamente NÃO vamos abordar
- [Segmento A]: Razão — [competing priority / não é rentável / complexidade alta]

---

## 3. Problema

### Problema primário
**Statement:**
Quando [contexto], [persona] quer [job], mas [friction/pain]. Resulta em [consequência].

**Evidência:**
- [X% de users mencionaram em entrevista]
- [Y data metric que valida]
- [Z competitors tentam resolver]

### Problema secundário
[Similar format]

---

## 4. Solução

### Diferenciação
**Posicionamento:**
[Seu produto] é [tipo] que [diferenciação única], diferente de [competitors] porque [razão].

### Features principais (próx. 2-3 trimestres)
1. **Feature A**: Resolve [problema] de forma [diferente]
2. **Feature B**: Só nós fazemos isso
3. **Feature C**: Fazemos 10x melhor que competitors

### Investimentos críticos
- [Investimento técnico/design/brand que vai fazer diferença]

---

## 5. Monetização

### Modelo de receita
- [Subscription / Usage-based / Freemium / Enterprise]: [Razão]

### Pricing
- **Tier 1**: [Preço] para [segmento]
- **Tier 2**: [Preço] para [segmento]
- **Tier 3**: [Preço] para [segmento]

### Benchmark
- Salários/custos salvos: $[X] / ano por cliente
- Disposição a pagar: $[Y] (de entrevistas)
- Pricing de competitors: $[Z]

### Expansão de receita
- [Upgrade path — como expand existing customer]
- [Cross-sell — como vender mais na base]

---

## 6. Métricas (Success Metrics)

### Métrica de negócio (o que mais importa)
- **MRR Growth**: 10% month-over-month
- **Churn**: < 5% month-over-month
- **CAC**: < $[X]
- **LTV**: > $[Y] (LTV:CAC ratio > 3)

### Métricas de produto (indicadores)
- **Engagement**: X% monthly active
- **Feature adoption**: X% using [core feature]
- **NPS**: Target [X]

### Métrica de segmento (se variável)
- [Segmento A]: [Métrica específica]
- [Segmento B]: [Métrica específica]

---

## 7. Roadmap (Próximos 3 trimestres)

### Q[X]: [Tema]
- Goal: [O que vamos conseguir]
- Features: [3-5 features principais]
- Impacto: [Métrica que move]
- Recursos: [Team alocação]

### Q[X+1]: [Tema]
- Goal: [...]
- Features: [...]
- Impacto: [...]

### Q[X+2]: [Tema]
- Goal: [...]
- Features: [...]
- Impacto: [...]

---

## 8. Riscos e Mitigações

| Risk | Probabilidade | Impacto | Mitigação |
|------|-----------|--------|----------|
| [Competitor move] | Alta | Alto | [O que fazemos] |
| [Market shift] | Média | Médio | [O que fazemos] |
| [Tech blocker] | Baixa | Alto | [O que fazemos] |

---

## 9. Call to Action

### Próximo passo
1. [Primeira coisa a fazer — ex: validar hipótese X]
2. [Segunda coisa — ex: hire para role Y]
3. [Terceira coisa — ex: preparar roadmap detalhado]

### Timeline
- [Data]- [Data]: [O que fazemos]

### Quem decide o quê
- PM: [Decisão]
- Eng Lead: [Decisão]
- Executive: [Decisão]

---

## Aprovação

- [ ] CEO/Founder: Alinhado com visão de negócio
- [ ] PM: Viável com time e resources alocados
- [ ] Eng Lead: Tech stack permite implementação
- [ ] Finance: Financeiramente faz sentido

**Versão**: 1.0
**Última atualização**: [Data]
**Próxima review**: [3 meses, ou se contexto muda]

Read the full file on GitHub · 426 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.

  1. 8d ago First seen · 426 lines · 0 tokens per session scan A 6309a5fc11e0

Subscribe to this mod's changes

strategy 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 3,333 tokens. A static security scan graded it A with 0 findings. It is 100% identical to strategy, differing in 0 lines, and is treated as a copy.