phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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/phuryn/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/commands/phuryn/pm-skills/strategy)<a href="https://agentmods.dev/commands/phuryn/pm-skills/strategy"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/strategy/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/commands/phuryn/pm-skills/strategy"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/strategy.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.00018 | $0.01005 |
| Opus 5 | $0.00009 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/strategy -- Product Strategy Canvas
Build a complete product strategy document using the 9-section Product Strategy Canvas. Covers vision, segments, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
Invocation
/strategy AI-powered design tool for non-designers
/strategy [upload existing strategy doc, pitch deck, or business plan]
/strategy # asks about your product
Workflow
Step 1: Understand the Product
Accept context from:
- Product description (verbal or written)
- Uploaded documents (strategy decks, pitch decks, PRDs, business plans)
- Existing strategy to refine or challenge
Ask key questions:
- What does the product do? Who is it for?
- What stage is it in? (idea, MVP, growth, mature)
- What's the business model?
- What triggered the need for a strategy document? (new product, pivot, annual planning, fundraise)
Step 2: Build the Strategy Canvas
Apply the product-strategy and product-vision skills:
Work through all 9 sections of the Strategy Canvas:
- Vision: Inspiring north star that motivates the team
- Target Segments: Who you serve (and who you don't)
- Pain Points & Value: Problems you solve and the value you create
- Value Propositions: JTBD-framed value for each segment
- Strategic Trade-offs: What you choose NOT to do (as important as what you do)
- Key Metrics: How you measure success
- Growth Engine: How you acquire and expand users
- Core Capabilities: What you need to build and maintain
- Defensibility: What makes this hard to copy (network effects, data, brand, switching costs)
For each section, provide specific content — not generic advice.
Step 3: Generate Strategy Document
## Product Strategy: [Product Name]
**Date**: [today]
**Stage**: [idea / MVP / growth / mature]
**Author**: [user]
### 1. Vision
[Inspiring, achievable, emotional — 2-3 sentences max]
### 2. Target Segments
| Segment | Size | Pain Level | Current Alternative | Priority |
|---------|------|-----------|-------------------|----------|
**Primary segment**: [who and why]
**Explicitly not serving**: [who and why]
### 3. Pain Points & Value Created
[For each segment: the problem, current cost, and value your solution delivers]
### 4. Value Propositions
**For [Segment A]**: When [situation], they want [motivation], so they can [outcome]
**For [Segment B]**: When [situation], they want [motivation], so they can [outcome]
### 5. Strategic Trade-offs
| We Choose | Over | Because |
|-----------|------|---------|
### 6. Key Metrics
- **North Star**: [metric]
- **Input Metrics**: [3-5 levers]
- **Health Metrics**: [guardrails]
### 7. Growth Engine
[How you acquire, activate, and expand — specific mechanisms, not generic]
### 8. Core Capabilities
| Capability | Build / Buy / Partner | Investment Level | Timeline |
|-----------|---------------------|-----------------|----------|
### 9. Defensibility
[What creates a moat — be specific about which type: network effects, data, brand, switching costs, economies of scale]
### Strategic Risks
[Top 3 things that could invalidate this strategy]
### Next Steps
[What to do with this strategy — socialize, test, build]
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 · 119 lines · 18 tokens per session scan A 1e1c2dbe6028
strategy is a command published in the GitHub repository phuryn/pm-skills (26,507 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 1,005 once invoked, about $0.0001 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-09-15.
Other commands, from other repositories
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.
value-prop-statements
Fan an existing positioning statement out into segment- and channel-specific value-prop copy variants, trace-checked against drift.
pmm-metrics
Define a North Star Metric and capped scorecard, or audit an existing metrics list for sprawl and vanity metrics.
alternatives-map
Build or deepen your competitive alternatives map — direct competitors, adjacent tools, DIY, and status quo — from real win/loss data.
gtm-motions
Score and select a GTM motion stack against real deal economics, not a taxonomy tour.
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.