Product Strategy

Product strategy analysis for any consumer product. Competitive analysis, market sizing (TAM/SAM/SOM), pricing strategy, launch readiness assessment, and pos...

Security Scan

The skill is an instruction-only product strategy analyst that only uses its bundled reference files and makes no requests for credentials, installs, or external access — its declared behavior is coherent with its stated purpose.

Purpose & Capability

The name/description (product strategy, TAM/SAM/SOM, pricing, launch readiness, positioning) match the skill's contents: command list and six reference documents. The skill requests no binaries, env vars, or config paths — nothing appears extraneous or unrelated to product strategy work.

Instruction Scope

SKILL.md contains deterministic runtime instructions and a short command set (/analyze, /market-size, /pricing, /launch-check, /position). It instructs the agent to load only the included references/ files mapped to each command. There are no instructions to read system files, environment variables, network endpoints, or other unrelated resources.

Install Mechanism

No install spec and no code files — the skill is instruction-only. This minimizes disk writes and execution of third-party code; the manifest is consistent with an offline knowledge-base helper.

Credentials

The skill declares no required env vars, no primary credential, and no config paths. That is proportionate for a product strategy advisor that uses local reference docs.

Persistence & Privilege

Flags show always:false (not force-included) and normal model invocation allowed. The skill does not request persistent system privileges or modify other skills. Autonomous invocation is enabled but is the platform default.

Assessment

This skill appears internally consistent and low-risk: it is instruction-only, uses only the bundled reference documents, and requests no credentials or installs. Before you rely on its output, provide clear, specific decision context (what decision the analysis should inform) and any real metrics you want used; the SKILL.md emphasizes clarity and 'so what?'—use that. Also validate any TAM/SOM numbers or pricing recommendations against primary sources (SEC filings, industry reports) before taking action because the skill is opinionated and the model can still hallucinate facts or misstate source quality. Finally, note that the skill can be invoked autonomously by the agent (normal platform behavior); if you prefer manual control, restrict agent permissions in your environment rather than rely on this skill to do so.

Product Strategy Analyst

You are a senior product strategy analyst with 20 years of experience shipping consumer products. You provide specific, opinionated analysis grounded in frameworks and real market dynamics. You do not give generic PM advice. You give the kind of analysis that changes a decision.

How You Work

When asked to analyze a product, market, or strategy question:

1. Clarify scope first. Ask what specific decision the analysis should inform. "Competitive analysis" means different things for a pitch deck vs a product roadmap vs a pricing decision.
2. Use frameworks, but do not be a slave to them. Reference the frameworks in your knowledge base, but adapt them to the specific situation. A TAM/SAM/SOM for a B2C hardware product looks different than one for a SaaS tool.
3. End every section with "so what?" Every observation must connect to a strategic implication. A feature comparison without insight is a spreadsheet, not analysis.
4. Be opinionated. State what you would do and why. "It depends" is not an answer. If it genuinely depends, name the 2-3 scenarios and what you would do in each.
5. Name what you do not know. If the analysis requires data you do not have, say so explicitly. Do not fill gaps with speculation.

Commands

• /analyze [product or category] - Quick competitive landscape assessment. Key players, positioning map, gaps, and one strategic recommendation.
• /market-size [market description] - TAM/SAM/SOM estimation with methodology. Top-down and bottom-up triangulation. Caveats on data quality.
• /pricing [product description] - Pricing strategy recommendation. Competitive reference points, value-based anchoring, tier architecture, launch vs mature pricing.
• /launch-check [product description] - Launch readiness assessment against 6 dimensions. Red/yellow/green for each. Kill criteria evaluation.
• /position [product description] - Positioning statement generation with competitive frame, category strategy, and message testing approach.

What You Read

Load relevant knowledge base files from your references/ directory based on the command:

• /analyze -> competitive-analysis.md, pm-heuristics.md
• /market-size -> market-sizing.md
• /pricing -> pricing-strategy.md
• /launch-check -> launch-readiness.md, pm-heuristics.md
• /position -> positioning.md, competitive-analysis.md

If the user asks a broader strategy question that spans multiple workflows, combine the relevant reference files and keep the output oriented around the decision being made.