Borrowing it
Nothing to install: this file belongs to karlng279/ai-ready-product-workflow-v2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/karlng279/ai-ready-product-workflow-v2/main/.claude/commands/pm-strategy.mdgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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/karlng279/ai-ready-product-workflow-v2/pm-strategy)<a href="https://agentmods.dev/commands/karlng279/ai-ready-product-workflow-v2/pm-strategy"><img src="https://agentmods.dev/badge/commands/karlng279/ai-ready-product-workflow-v2/pm-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/karlng279/ai-ready-product-workflow-v2/pm-strategy"><img src="https://agentmods.dev/badge/commands/karlng279/ai-ready-product-workflow-v2/pm-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.00000 | $0.00952 |
| Opus 5 | $0.00000 | $0.00476 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
pm-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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pm-strategy
Start a product strategy session. Produces a structured strategy artifact using PM frameworks.
Usage
/pm-strategy [product or feature name]
If a product/feature name is provided via $ARGUMENTS, use it. Otherwise ask: "What product or initiative are we building strategy for?"
What This Command Does
Activates the pm-product-strategy skill and guides a focused strategy session. The output is a strategy artifact stored in features/{feature-name}/pm/strategy.md (or a standalone pm/strategy.md if this is a product-level strategy).
Session Flow
Step 1 — Context Gathering
Ask the user (sequentially, not all at once):
- "What problem does this product/feature solve? Who has this problem?"
- "What's your current thinking on the target market or user segment?"
- "Do you have existing research, metrics, or competitor context to share?"
- "What does success look like in 6–12 months?"
Accept whatever the user provides — incomplete answers are fine. The skill will surface gaps through the frameworks.
Step 2 — Framework Selection
Based on what the user shares, activate pm-product-strategy skill and apply the most relevant frameworks:
| User Context | Primary Framework |
|---|---|
| Early-stage, problem unclear | Jobs-to-be-Done strategic lens |
| Market positioning question | Product Strategy Canvas + Competitive Positioning Map |
| Goal-setting or planning cycle | OKR hierarchy (Objective → Key Results → Initiatives) |
| Competitive threat or expansion | SWOT + Ansoff Matrix |
| Full strategy session | All frameworks sequentially |
Always start with the Product Strategy Canvas as the primary structure.
Step 3 — Strategy Generation
Activate pm-product-strategy skill. Read pm-framework/product-strategy/rules.md before generating output.
Produce the following sections based on what the user has shared:
1. Product Vision & Mission
- Vision statement (inspirational, long-term, customer-outcome focused)
- Mission statement (operational, what you do and for whom)
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.
- 11d ago First seen · 128 lines · 0 tokens per session scan A cfb871bf2c9c
pm-strategy is a command published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 952 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.